guyben 2d4eeae26c Fix admin access to registryAdminClientId when they aren't associated with it ... An admin that isn't associated with any clientId, will default to the registryAdminClientId. However, if we set the registryAdminClientId as the session's CLIENT_ID_ATTRIBUTE, the next time we access the server we have a client-id attribute we aren't associated with - which returns a "403 Registrar Console access revoked" error (the assumption is - we were associated with it before but aren't anymore) To fix this - we just add all admins as "hasAccessTo" registryAdminClientId, even if it's not in the contacts. This will let admins stay on the admin registrar, without affecting where they log-in initially if they are also contacts in different registrars. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=200402856		2018-06-18 18:04:56 -04:00
..
com/google/testing/builddefs	Replace PACKAGE_NAME with package_name() in bzl files.	2018-04-02 16:18:55 -04:00
google/registry	Fix admin access to registryAdminClientId when they aren't associated with it	2018-06-18 18:04:56 -04:00