-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ability to precreate enterprise users in Portal (and AGOL?) #118
Comments
Maybe it is as simple as adding the email domain to be a field on the AGOL model and then logic to check what has been submitted by the user? |
Some of the assumptions so far:
@jlherring @tbock Will ALL EPA users be required to use their Login.gov accounts to access GeoPortal (AGOL)? Or will EPA ppl still be using named accounts as well on GeoPlatform? |
@rdmccann EPA users on AGOL are automatically created via enterprise auth only. I see we could now pre-create them with this change but I don't think we need to (or is it harder to not deal with this?). |
@tbock If EPA users are submitting requests through this tool for access to AGOL, I think we need to deal with it now. Otherwise it will show the option to manually set a password for those accounts or try to invite the user with the named account process. |
@jlherring have we ever had what should be an enterprise account accidentally created through the tool? Maybe it doesn't matter and the enterprise login username generation just moves on to another username? |
so we've had EPA ppl request through the tool and it made them a guest acct when they didn't need one, but as far as I've seen, never created an enterprise acct |
Per documentation is it possible to precreate an enterprise user in portal. https://developers.arcgis.com/rest/enterprise-administration/portal/create-user.htm
The system has only been built to create "arcgis" based users in AGOL so far. Perhaps a change to the AGOL model indicating if enterprise user create is allowed and then figure out how to detect if a request is a enterprise users. This is likely simply checking the email address (anything @epa.gov should be able to use enterprise auth).
The text was updated successfully, but these errors were encountered: