Just setting up Portal... seems anyone that hits "Register" gets assigned a new account instantly. How do I require that a registration request be approved by an administrator role?
Just setting up Portal... seems anyone that hits "Register" gets assigned a new account instantly. How do I require that a registration request be approved by an administrator role?
Strangely, this isn't working. I can try and add this property, but then after a minute or so the page refreshes and the property is not set.
Yep, and typed in rather than copy pasted (to prevent extra characters being pasted in). Still doesn't work, curious.
Also working on 10.5.1 on Linux. Hmm, do you think changing this through the web adaptor rather than on the server makes any difference? I accessed the admin page through the web adaptor to make these changes.
I doubt it - I also went though my web adaptor (on Tomcat, installed on the same box as my Portal). Is there anything notable in the portal logs?
Nothing notable. Also using Tomcat.
I do get, "The web server was found to be stopped. Restarting it" which coincides with my attempts to update properties. Maybe there is issue where it knows it has to restart Portal to apply changes, but it is reloading an old configuration as it does so for some reason?
Whelp…without something more solid, you could:
1. Stop the portal
2. Make a backup of /portal/customizations/10.5.1/webapps/arcgis#home/js/arcgisonline/config.js
3. Open this file in your favorite text editor and set the showSignUp property to false,
4. Start the portal back up again.
Note: This workflow is very unsupported. Have a backup of config.js handy. No warranty is expressed or implied. Mileage may vary.
Hey Randall,
I reached out to ESRI support before going forward with that idea Luckily we figured out this issue.
I already had a property set in the portal system settings. For some reason it didn't occur to me to add additional properties in the same bracket.
This is what I was doing:
{"WebContextURL":[webcontextURL]}
{"disableSignup": "true"}
This wasn't working because, as soon as the first property was read, it wouldn't search for the next set of brackets! As soon as I realized what was happening, I felt silly.
What I needed was this:
{"WebContextURL": [webcontextURL], "disableSignup": "true"}
Once I did this, it worked without issue.
Hopefully leaving this explanation here might help someone else as well
{"disableSignup": "true"} works only partially on my fresh install of Portal 10.5.1. There is no "Create account" on plain login page, but:
With those issues we aren't able to publish our Portal to the Internet. Any solution for above issues?
It is still present at 10.6. You can change it by setting advanced portal options (see how) and changing signup variable to something neutral, eg.
signup: "index.html"
Regards
Kuba
Did you try Disabling anonymous access—Portal for ArcGIS (10.5.x) | ArcGIS Enterprise ?
- Sign in to the portal website as an Administrator of your organization and click the Edit Settings button.
- Click the Security link on the left side of the page.
- Uncheck the Allow anonymous access to your portal option.
- Click Save to apply your change.
If you're using web tier authentication (that is, you're performing authentication through ArcGIS Web Adaptor), disable anonymous access on your web server (For Windows).
Thanks Jayanta... but are you sure this applies to my situation? I don't want to restrict people from seeing the Portal resources outside of the organization; I want to restrict the ability to request for accounts without administrative approval. As it is, merely clicking "Create Account" instantly creates an account.
Disabling anonymous access will disable the option of registering to Portal by anonymous users from the landing page. Only those users can login, whose account have been created by the administrator (existing users).
All the maps that have been shared with public on landing page, could be seen by all the users without creating logins.
Thanks for the clarification. That does sound like it would solve the issue.
I was expecting the ability to have people request accounts that are then approved by administrator. That would have reduced the administrative headache of getting everyone's contact info ahead of time and creating accounts for them. Nonetheless, this is better than allowing just anyone to request an account! Hopefully this solves the issue, though I am still curious and unsure why Randall's suggestion was not working.
HI Cassandra,
Here's the doc for this:
http://server.arcgis.com/en/portal/latest/administer/linux/disabling-users-ability-to-create-builtin-portal-accounts.htm