Re: [db-wg] RIPE Access Account: Cannot change registered e-mail address back to previously one
Dear Christoffer, Unfortunately this is not as easy to implement as one might think. However, we will look into this again and see if we can find a solution for this issue. Kind regards Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC
On 10 Oct 2017, at 21:16, Christoffer Hansen via db-wg <db-wg@ripe.net> wrote:
From: Christoffer Hansen via db-wg <db-wg@ripe.net> Subject: [db-wg] RIPE Access Account: Cannot change registered e-mail address back to previously one To: RIPE Database Working Group <db-wg@ripe.net> Reply-To: Christoffer Hansen <netravnen@gmail.com>
From: Christoffer Hansen <netravnen@gmail.com> Subject: RIPE Access Account: Cannot change registered e-mail address back to previously one Date: 10 October 2017 at 19:52:50 GMT+2 To: RIPE Database Working Group <db-wg@ripe.net>
RIPE Database Working Group <db-wg@ripe.net>
Am I the only one who have previously wondered about the following issue... (?)
1. Register a RIPE Access Account with [account_1@example.com] 2. is changed to [account_2@example.com] 3. later tries to change registered RIPE Access Account e-mail back to [account_1@example.com].
I'am not allowed to do this.
RIPE NCC's website simply does *not* allow me to do this.
Refer to the following pictures for clarification.
Changing the e-mail address back to [account_1@example.com] <2017-10-10 19_00_24-RIPE NCC Access — RIPE Network Coordination Centre.png> ×
Creating a new RIPE Access Account for [account_1@example.com] <2017-10-10 19_03_18-RIPE NCC Access — RIPE Network Coordination Centre.png> ×
Trying the forgotten password function for [account_1@example.com] <2017-10-10 19_04_28-RIPE NCC Access — RIPE Network Coordination Centre.png> ×
Regards, Christoffer Hansen. gpg: c8b3 82a8 a1cd cdb7 71fe b24c c654 948f da86 becd
Dear Tim Would it be possible for you to provide reference to earlier discussion(s) about the issue ? Or clarify what in the RIPE NCC Database design prevents the issue from being easy to resolve ? Regards, Christoffer. gpg: c8b3 82a8 a1cd cdb7 71fe b24c c654 948f da86 becd On 10/11/2017 14:24, Tim Bruijnzeels wrote:
Dear Christoffer,
Unfortunately this is not as easy to implement as one might think. However, we will look into this again and see if we can find a solution for this issue.
Kind regards
Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC
On 10 Oct 2017, at 21:16, Christoffer Hansen via db-wg <db-wg@ripe.net> wrote:
From: Christoffer Hansen via db-wg <db-wg@ripe.net> Subject: [db-wg] RIPE Access Account: Cannot change registered e-mail address back to previously one To: RIPE Database Working Group <db-wg@ripe.net> Reply-To: Christoffer Hansen <netravnen@gmail.com>
From: Christoffer Hansen <netravnen@gmail.com> Subject: RIPE Access Account: Cannot change registered e-mail address back to previously one Date: 10 October 2017 at 19:52:50 GMT+2 To: RIPE Database Working Group <db-wg@ripe.net>
RIPE Database Working Group <db-wg@ripe.net>
Am I the only one who have previously wondered about the following issue... (?)
1. Register a RIPE Access Account with [account_1@example.com] 2. is changed to [account_2@example.com] 3. later tries to change registered RIPE Access Account e-mail back to [account_1@example.com].
I'am not allowed to do this.
RIPE NCC's website simply does *not* allow me to do this.
Refer to the following pictures for clarification.
Changing the e-mail address back to [account_1@example.com] <2017-10-10 19_00_24-RIPE NCC Access — RIPE Network Coordination Centre.png> ×
Creating a new RIPE Access Account for [account_1@example.com] <2017-10-10 19_03_18-RIPE NCC Access — RIPE Network Coordination Centre.png> ×
Trying the forgotten password function for [account_1@example.com] <2017-10-10 19_04_28-RIPE NCC Access — RIPE Network Coordination Centre.png> ×
Regards, Christoffer Hansen. gpg: c8b3 82a8 a1cd cdb7 71fe b24c c654 948f da86 becd
Dear Christopher, This is not a limitation of the RIPE Database. This is a limitation in the RIPE NCC Access account system, which is based on a third party application. Emails are used as the primary key for the account, and therefore changing emails has turned out to be troublesome. In retrospect supporting changing emails may not have been a good idea to begin with. For the most part it does work, but a small fraction of our users, you included, is affected by this issue. But, as I said, we will look into solutions. Thanks Tim
On 11 Oct 2017, at 15:34, Christoffer Hansen <netravnen@gmail.com> wrote:
Dear Tim
Would it be possible for you to provide reference to earlier discussion(s) about the issue ? Or clarify what in the RIPE NCC Database design prevents the issue from being easy to resolve ?
Regards, Christoffer. gpg: c8b3 82a8 a1cd cdb7 71fe b24c c654 948f da86 becd On 10/11/2017 14:24, Tim Bruijnzeels wrote:
Dear Christoffer,
Unfortunately this is not as easy to implement as one might think. However, we will look into this again and see if we can find a solution for this issue.
Kind regards
Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC
On 10 Oct 2017, at 21:16, Christoffer Hansen via db-wg <db-wg@ripe.net> wrote:
From: Christoffer Hansen via db-wg <db-wg@ripe.net> Subject: [db-wg] RIPE Access Account: Cannot change registered e-mail address back to previously one To: RIPE Database Working Group <db-wg@ripe.net> Reply-To: Christoffer Hansen <netravnen@gmail.com>
From: Christoffer Hansen <netravnen@gmail.com> Subject: RIPE Access Account: Cannot change registered e-mail address back to previously one Date: 10 October 2017 at 19:52:50 GMT+2 To: RIPE Database Working Group <db-wg@ripe.net>
RIPE Database Working Group <db-wg@ripe.net>
Am I the only one who have previously wondered about the following issue... (?)
1. Register a RIPE Access Account with [account_1@example.com] 2. is changed to [account_2@example.com] 3. later tries to change registered RIPE Access Account e-mail back to [account_1@example.com].
I'am not allowed to do this.
RIPE NCC's website simply does *not* allow me to do this.
Refer to the following pictures for clarification.
Changing the e-mail address back to [account_1@example.com] <2017-10-10 19_00_24-RIPE NCC Access — RIPE Network Coordination Centre.png> ×
Creating a new RIPE Access Account for [account_1@example.com] <2017-10-10 19_03_18-RIPE NCC Access — RIPE Network Coordination Centre.png> ×
Trying the forgotten password function for [account_1@example.com] <2017-10-10 19_04_28-RIPE NCC Access — RIPE Network Coordination Centre.png> ×
Regards, Christoffer Hansen. gpg: c8b3 82a8 a1cd cdb7 71fe b24c c654 948f da86 becd
Dear Tim I was not aware the *RIPE NCC Access account system* was a separate system apart from the *RIPE Database system*. In retrospect supporting changing emails may not have been a good idea to
begin with
I think this was a great idea, as account emails can change as people shift employers and/or email providers shuts down. One is not forced to create a new RIPE NCC Access account everytime the email address changes. Handling the changing email process is rightly so another matter for another discussion. Regards, Christoffer. gpg: c8b3 82a8 a1cd cdb7 71fe b24c c654 948f da86 becd On 11 October 2017 at 20:58, Tim Bruijnzeels <tim@ripe.net> wrote:
Dear Christopher,
This is not a limitation of the RIPE Database.
This is a limitation in the RIPE NCC Access account system, which is based on a third party application. Emails are used as the primary key for the account, and therefore changing emails has turned out to be troublesome. In retrospect supporting changing emails may not have been a good idea to begin with. For the most part it does work, but a small fraction of our users, you included, is affected by this issue. But, as I said, we will look into solutions.
Thanks Tim
On 11 Oct 2017, at 15:34, Christoffer Hansen <netravnen@gmail.com> wrote:
Dear Tim
Would it be possible for you to provide reference to earlier discussion(s) about the issue ? Or clarify what in the RIPE NCC Database design prevents the issue from being easy to resolve ?
Dear Christoffer,
Unfortunately this is not as easy to implement as one might think. However, we will look into this again and see if we can find a solution for
Regards, Christoffer. gpg: c8b3 82a8 a1cd cdb7 71fe b24c c654 948f da86 becd On 10/11/2017 14:24, Tim Bruijnzeels wrote: this issue.
Kind regards
Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC
On 10 Oct 2017, at 21:16, Christoffer Hansen via db-wg <db-wg@ripe.net>
wrote:
From: Christoffer Hansen via db-wg <db-wg@ripe.net> Subject: [db-wg] RIPE Access Account: Cannot change registered e-mail
address back to previously one
To: RIPE Database Working Group <db-wg@ripe.net> Reply-To: Christoffer Hansen <netravnen@gmail.com>
From: Christoffer Hansen <netravnen@gmail.com> Subject: RIPE Access Account: Cannot change registered e-mail address back to previously one Date: 10 October 2017 at 19:52:50 GMT+2 To: RIPE Database Working Group <db-wg@ripe.net>
RIPE Database Working Group <db-wg@ripe.net>
Am I the only one who have previously wondered about the following issue... (?)
1. Register a RIPE Access Account with [account_1@example.com] 2. is changed to [account_2@example.com] 3. later tries to change registered RIPE Access Account e-mail back to [account_1@example.com].
I'am not allowed to do this.
RIPE NCC's website simply does *not* allow me to do this.
Refer to the following pictures for clarification.
Changing the e-mail address back to [account_1@example.com] <2017-10-10 19_00_24-RIPE NCC Access — RIPE Network Coordination Centre.png> ×
Creating a new RIPE Access Account for [account_1@example.com] <2017-10-10 19_03_18-RIPE NCC Access — RIPE Network Coordination Centre.png> ×
Trying the forgotten password function for [account_1@example.com] <2017-10-10 19_04_28-RIPE NCC Access — RIPE Network Coordination Centre.png> ×
Regards, Christoffer Hansen. gpg: c8b3 82a8 a1cd cdb7 71fe b24c c654 948f da86 becd
Dear Christoffer,
On 12 Oct 2017, at 08:40, Christoffer Hansen <netravnen@gmail.com> wrote:
Dear Tim
I was not aware the RIPE NCC Access account system was a separate system apart from the RIPE Database system.
In retrospect supporting changing emails may not have been a good idea to begin with
I think this was a great idea, as account emails can change as people shift employers and/or email providers shuts down. One is not forced to create a new RIPE NCC Access account everytime the email address changes.
And that’s why we did it. But it has its own set of problems. For auditing purposes we need to keep track in some systems (e.g. RPKI history) which account made a specific change, or sent a specific request. However, there are problems when people hand over their personal SSO account to someone completely different, or when shared (role) accounts are used. This gets very messy, is hard to detect for the machines, and unfortunately this is a common practice. Creating a different account with an easy way to migrate existing authorisations from the old to the new account might have been a better idea.
Handling the changing email process is rightly so another matter for another discussion.
In any case, yes. We already have a change process and we are looking into facilitating changing back to an email address used earlier on that *specific* account. Regards Tim
Regards, Christoffer. gpg: c8b3 82a8 a1cd cdb7 71fe b24c c654 948f da86 becd
On 11 October 2017 at 20:58, Tim Bruijnzeels <tim@ripe.net> wrote: Dear Christopher,
This is not a limitation of the RIPE Database.
This is a limitation in the RIPE NCC Access account system, which is based on a third party application. Emails are used as the primary key for the account, and therefore changing emails has turned out to be troublesome. In retrospect supporting changing emails may not have been a good idea to begin with. For the most part it does work, but a small fraction of our users, you included, is affected by this issue. But, as I said, we will look into solutions.
Thanks Tim
On 11 Oct 2017, at 15:34, Christoffer Hansen <netravnen@gmail.com> wrote:
Dear Tim
Would it be possible for you to provide reference to earlier discussion(s) about the issue ? Or clarify what in the RIPE NCC Database design prevents the issue from being easy to resolve ?
Regards, Christoffer. gpg: c8b3 82a8 a1cd cdb7 71fe b24c c654 948f da86 becd On 10/11/2017 14:24, Tim Bruijnzeels wrote:
Dear Christoffer,
Unfortunately this is not as easy to implement as one might think. However, we will look into this again and see if we can find a solution for this issue.
Kind regards
Tim Bruijnzeels Assistant Manager Software Engineering RIPE NCC
On 10 Oct 2017, at 21:16, Christoffer Hansen via db-wg <db-wg@ripe.net> wrote:
From: Christoffer Hansen via db-wg <db-wg@ripe.net> Subject: [db-wg] RIPE Access Account: Cannot change registered e-mail address back to previously one To: RIPE Database Working Group <db-wg@ripe.net> Reply-To: Christoffer Hansen <netravnen@gmail.com>
From: Christoffer Hansen <netravnen@gmail.com> Subject: RIPE Access Account: Cannot change registered e-mail address back to previously one Date: 10 October 2017 at 19:52:50 GMT+2 To: RIPE Database Working Group <db-wg@ripe.net>
RIPE Database Working Group <db-wg@ripe.net>
Am I the only one who have previously wondered about the following issue... (?)
1. Register a RIPE Access Account with [account_1@example.com] 2. is changed to [account_2@example.com] 3. later tries to change registered RIPE Access Account e-mail back to [account_1@example.com].
I'am not allowed to do this.
RIPE NCC's website simply does *not* allow me to do this.
Refer to the following pictures for clarification.
Changing the e-mail address back to [account_1@example.com] <2017-10-10 19_00_24-RIPE NCC Access — RIPE Network Coordination Centre.png> ×
Creating a new RIPE Access Account for [account_1@example.com] <2017-10-10 19_03_18-RIPE NCC Access — RIPE Network Coordination Centre.png> ×
Trying the forgotten password function for [account_1@example.com] <2017-10-10 19_04_28-RIPE NCC Access — RIPE Network Coordination Centre.png> ×
Regards, Christoffer Hansen. gpg: c8b3 82a8 a1cd cdb7 71fe b24c c654 948f da86 becd
participants (2)
-
Christoffer Hansen -
Tim Bruijnzeels