--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/1e9928ee-871a-4fb9-820d-ba178881e747%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi Jamie,I'm glad you wrote because I've been meaning to follow up with you on your other user-related questions on Tuesday's community call. I hope you find the additions I made to the notes after the call helpful: https://groups.google.com/d/msg/dataverse-community/op753PRmoUY/mm7GAGoaAgAJI guess my first question is why you want to use the API to create the user? Why not use the GUI and sign up with an email address you control (from Yahoo or whatever) and then change the email address to the visiting researcher afterwards? Are you expecting a log of visiting researchers leading you to want to automate this process? Or is it that you don't want the "Sign Up" link to appear? If so, the API is for you. :)Yes, "BuiltinUsers.Key" is different than any API token that a user might have. The terminology is confusing. For developers the "BuiltinUsers.Key" is "burrito" but for production installations the burrito is deleted or eaten or whatever[1]. So you have to add "taco" or something[2], like this:curl -X PUT -d taco http://localhost:8080/api/admin/settings/BuiltinUsers.KEYThen you create your user as described at http://guides.dataverse.org/en/4.13/api/native-api.html#create-a-builtin-userI hope this helps! Please keep the questions coming. :)Phil
On Thu, May 9, 2019 at 5:05 PM Jamie Jamison <jam...@g.ucla.edu> wrote:
Is the BuiltinUsers.Key the api key or is this a different key I create?--For dataverse.ucla.edu users come in via Shibboleth, other authentications have been blocked. But I wanted to be able to create a local/builtin account from the api for exceptions such as visiting researcher.Thank you,Jamie
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/1e9928ee-871a-4fb9-820d-ba178881e747%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
:AllowSignUp
is set to “false” per the Configuration section to prevent users from creating local accounts via the web interface. Phil,Thank you again. The notes were very helpful. I'm working my way through the list of what needs to be done. I'd say I'm doing the easiest to hardest but after surviving my upgrade of postgresql everything seems easier by comparison.Why we decided to only add local users through the API is so the only time someone can create a dataverse is when they login - even for the first time - though shibboleth. Most of the time we are limiting to UCLA affiliated but creating a local account for the exceptions.I may be wrong here but I thought that if the GUI is available then anyone can create an account, UCLA or not. They do have to accept the terms but I've noticed no one seems to read what they click on.Jamie
On Thursday, May 9, 2019 at 4:01:28 PM UTC-7, Philip Durbin wrote:
Hi Jamie,I'm glad you wrote because I've been meaning to follow up with you on your other user-related questions on Tuesday's community call. I hope you find the additions I made to the notes after the call helpful: https://groups.google.com/d/msg/dataverse-community/op753PRmoUY/mm7GAGoaAgAJI guess my first question is why you want to use the API to create the user? Why not use the GUI and sign up with an email address you control (from Yahoo or whatever) and then change the email address to the visiting researcher afterwards? Are you expecting a log of visiting researchers leading you to want to automate this process? Or is it that you don't want the "Sign Up" link to appear? If so, the API is for you. :)Yes, "BuiltinUsers.Key" is different than any API token that a user might have. The terminology is confusing. For developers the "BuiltinUsers.Key" is "burrito" but for production installations the burrito is deleted or eaten or whatever[1]. So you have to add "taco" or something[2], like this:curl -X PUT -d taco http://localhost:8080/api/admin/settings/BuiltinUsers.KEYThen you create your user as described at http://guides.dataverse.org/en/4.13/api/native-api.html#create-a-builtin-userI hope this helps! Please keep the questions coming. :)Phil
On Thu, May 9, 2019 at 5:05 PM Jamie Jamison <jam...@g.ucla.edu> wrote:
Is the BuiltinUsers.Key the api key or is this a different key I create?--For dataverse.ucla.edu users come in via Shibboleth, other authentications have been blocked. But I wanted to be able to create a local/builtin account from the api for exceptions such as visiting researcher.Thank you,Jamie
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/1e9928ee-871a-4fb9-820d-ba178881e747%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin
--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/fa652ea7-1dd6-46bf-9210-a9e91fc30e1e%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CADL9p-WV8CA15se_Cejw1D0rNVkUbRD9DBN9QLkK_B5Ruc3gUg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to a topic in the Google Groups "Dataverse Users Community" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dataverse-community/EXApk46Jm2I/unsubscribe.
To unsubscribe from this group and all its topics, send an email to dataverse-commu...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CADL9p-WV8CA15se_Cejw1D0rNVkUbRD9DBN9QLkK_B5Ruc3gUg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/1e9928ee-871a-4fb9-820d-ba178881e747%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin
--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/fa652ea7-1dd6-46bf-9210-a9e91fc30e1e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsub...@googlegroups.com.
To post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CADL9p-WV8CA15se_Cejw1D0rNVkUbRD9DBN9QLkK_B5Ruc3gUg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
I resolved this issue simply by using the configuration option :SignUpUrl and pointing it to the custom survey page for external members to request for an account. curl -X PUT -d '/dataverseuser.xhtml?editMode=CREATE' http://localhost:8080/api/admin/settings/:SignUpUrl
Then I removed the configuration for :AllowSignUp, if this is set to False we cannot access the actual SignUpUrl which is https://dataverse.harvard.edu/dataverseuser.xhtml;jsessionid=1965ccb93b33ba0f69e88b29fa4f?editMode=CREATE&redirectPage=%2Fdataverse_homepage.xhtml.
Now this URL is only known to our administrators and they use this form to create the accounts as requested in the survey form. As per your other message through the UI, many checks have been put in place for creating secured password hence we need not worry about it. When the account is created it triggers an email to the external member and we advise them to reset the password and then login.
Prior to this setup we use to create the accounts at the backend using API and email the users the login details.
Hope this helps.
Let me know if you have any questions.
Regards
Venki
DR-NTU(Data) at NTU, Singapore.