Couldn't Create User Problem

48 views
Skip to first unread message

Sherry Lake

unread,
Jan 10, 2018, 5:10:22 PM1/10/18
to Dataverse Users Community
On our test server, not production, but would like some help.

I thought we fixed a user "identifier" problem (due to testing shibboleth accounts and others that were first created as builtin users), but we are getting this error (see attached file if it doesn't show here).

So this user is now trying to logon (creating account 1st) with our "real" shibboleth and is getting the above error.

I edited the authenticateduser table & changed all "Identifier" contents so they no longer match "real" shibboleth users.

Is there another field in authenticateduser table, do I need to change this field too: persistentUserId (I didn't).

Is there another table with usernames or identifiers?? What tables are updated when an account is created?


Oh, is there a diagram or info on ALL the tables (and their fields) in our PostSQL database?

Thanks,
Sherry




Screen Shot 2018-01-10 at 4.53.00 PM.png

Philip Durbin

unread,
Jan 10, 2018, 9:25:26 PM1/10/18
to dataverse...@googlegroups.com
Changing usernames is not supported and there are multiple tables in play. A procedure is described at https://github.com/IQSS/dataverse/issues/1445#issuecomment-251712762 but it's not for the feint of heart.

You can see a diagram of all the database tables at http://phoenix.dataverse.org/schemaspy/latest/relationships.html

I hope this helps get you started. At this point it might be better to email sup...@dataverse.org in case there's a lot of back and forth.

Phil

--
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-community@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/74a02428-0f53-4002-ab57-66e7bd8322ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--

Don Sizemore

unread,
Jan 11, 2018, 8:29:34 AM1/11/18
to dataverse...@googlegroups.com
> it's not for the feint of heart.

Phil beat me to responding, but during our Shibboleth testing I rendered multiple test Dataverse instances inoperable simply by modifying e-mail addresses. I strongly discourage editing any user information directly.

D

On Wed, Jan 10, 2018 at 9:25 PM, Philip Durbin <philip...@harvard.edu> wrote:
Changing usernames is not supported and there are multiple tables in play. A procedure is described at https://github.com/IQSS/dataverse/issues/1445#issuecomment-251712762 but it's not for the feint of heart.

You can see a diagram of all the database tables at http://phoenix.dataverse.org/schemaspy/latest/relationships.html

I hope this helps get you started. At this point it might be better to email sup...@dataverse.org in case there's a lot of back and forth.

Phil
On Wed, Jan 10, 2018 at 5:10 PM, Sherry Lake <shla...@gmail.com> wrote:
On our test server, not production, but would like some help.

I thought we fixed a user "identifier" problem (due to testing shibboleth accounts and others that were first created as builtin users), but we are getting this error (see attached file if it doesn't show here).

So this user is now trying to logon (creating account 1st) with our "real" shibboleth and is getting the above error.

I edited the authenticateduser table & changed all "Identifier" contents so they no longer match "real" shibboleth users.

Is there another field in authenticateduser table, do I need to change this field too: persistentUserId (I didn't).

Is there another table with usernames or identifiers?? What tables are updated when an account is created?


Oh, is there a diagram or info on ALL the tables (and their fields) in our PostSQL database?

Thanks,
Sherry




--
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+unsubscribe...@googlegroups.com.

To post to this group, send email to dataverse-community@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/74a02428-0f53-4002-ab57-66e7bd8322ae%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-community@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CABbxx8G7Pmv4iapU90TquZ16pQn3NibW3bTqGGAjEa73TJ3G0w%40mail.gmail.com.

Sherry Lake

unread,
Jan 11, 2018, 1:37:52 PM1/11/18
to Dataverse Users Community
So it seems it might be easier to blow away the database and start over? It is just our test machine.

Are the directions for Fresh Reinstall still good?

Or, we will just keep it the way it is. Seems the easiest.

Thanks for all the advice (and warnings)!
Sherry


On Thursday, January 11, 2018 at 8:29:34 AM UTC-5, Donald Sizemore II wrote:
> it's not for the feint of heart.

Phil beat me to responding, but during our Shibboleth testing I rendered multiple test Dataverse instances inoperable simply by modifying e-mail addresses. I strongly discourage editing any user information directly.

D
On Wed, Jan 10, 2018 at 9:25 PM, Philip Durbin <philip...@harvard.edu> wrote:
Changing usernames is not supported and there are multiple tables in play. A procedure is described at https://github.com/IQSS/dataverse/issues/1445#issuecomment-251712762 but it's not for the feint of heart.

You can see a diagram of all the database tables at http://phoenix.dataverse.org/schemaspy/latest/relationships.html

I hope this helps get you started. At this point it might be better to email sup...@dataverse.org in case there's a lot of back and forth.

Phil
On Wed, Jan 10, 2018 at 5:10 PM, Sherry Lake <shla...@gmail.com> wrote:
On our test server, not production, but would like some help.

I thought we fixed a user "identifier" problem (due to testing shibboleth accounts and others that were first created as builtin users), but we are getting this error (see attached file if it doesn't show here).

So this user is now trying to logon (creating account 1st) with our "real" shibboleth and is getting the above error.

I edited the authenticateduser table & changed all "Identifier" contents so they no longer match "real" shibboleth users.

Is there another field in authenticateduser table, do I need to change this field too: persistentUserId (I didn't).

Is there another table with usernames or identifiers?? What tables are updated when an account is created?


Oh, is there a diagram or info on ALL the tables (and their fields) in our PostSQL database?

Thanks,
Sherry




--
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.

--
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.

Philip Durbin

unread,
Jan 11, 2018, 1:44:23 PM1/11/18
to dataverse...@googlegroups.com
Those directions still seem fine to me. I can vouch for the phoenix "deploy" script that's mentioned. It gets run quite frequently.

To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-community+unsubscribe...@googlegroups.com.

--
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+unsubscribe...@googlegroups.com.

--
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-community@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/0af177e5-a3ad-4eba-a3af-2d386e1070a0%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages