My mistake! Unable to log in to gateway after creating new user with same name in a new internal usersource

Ignition
1

I think it's my mistake.
Unable to log in to gateway after creating new user with same name (other than the primary user) in a new internal usersource

Timeline of what I have setup
I have a quite fresh FrontEnd gateway setup with Primary and Redundant already connected and working
Until I broke it, The gateway had nothing else yet than two users (ex; userA userB) in the default user source, both Administrators
If it counts, it also has a remote tag provider connected to an IO server with identical user setup and a postgreSQL connection setup only on the IO server.
Both gateways have a project with different names and nothing else than one single memory tag to test the remote tag provider (that does not work yet as I get Error writing to tag with Bad_AccessDenied message)
If it counts, I already activated ignition on all servers, but on the Primary FrontEnd I had the "Emergency Ativation Mode" issue unsolved yet.

The problem occured (probably by my mistake to remember to avoid in the future)
when I created a new internal user source named Developers
and I added the seme userB here as an Administrator and added Administrator role in the Roles tab

I negected to delete the identical userB from the default user source
and went on to test userB login, I opened a new tab and acessed the designer, logged out from userA
and tryed userB but Login failed

from this poit, I'm unable to log in even with the untouched userA neither on pimary or secondary server

Since I am still connected with designer to it with userA, I created a page with User Management and was able to delete userB (probably from default)
but still unable to login to the gateway with the untouched userA. I even created userC and checked to be Administrator, but useless.

If I try to open a new designer connection, I get the same Login failed for any user.
I can still work in the unclosed designer where i am logged in as userA. can I do something from here to avoid a new reset?

Just to mention: I had the same problem at the first fresh setup a few days ago, when after defining the firt user at setup,
I had to reset because it did not let me log in at all with the newly created user.
Since than I have a temp usersouce that I was unable to delete, even after deleting userA from it at the same time as the above things happened.

setup: Lunx Ubuntu 24 desktop, Ignition v8.1.41

any advice other than do another password reset and comissioning and reconfigure everything from scratch?

I suppose I have to resert on both primary and secondary FrontEnd servers this time since already connected?
OBS:IOservers unaffected

and the most important thing: what to take care to avoid this in the future? avoid reuse of usernames? or avoid reuse of Roles? or probably avoid both.

I would appreciate any advice! Thanks

2

So, no access to the gateway configuration page ?

You can reset passwords from the gateway command line utility and log in with that.
I think what it does is create a new user source with a new admin in it, so make sure to clean things up afterward.

Once you're on the gateway page, go and make sure the user source / identity provider are setup correctly. It sounds like you're trying to log in against the wrong user source.

2 Likes
3

Yep! No access to anything. not even designer. only the unclosed deigner where I am still logged in. and acess to one empty(default template) perspective project that has no athetication requuired yet.

4

I already tryed that without any luck since at the very beginning I was unable to log in with the user just defined at setup and had to reset.
It does not allow me to delete the temp usersouce because it's dependent on the temp Identity Provider that can't be deleted either because of same temp usersource.

5

He ment this, this should allow you to log into everything again to fix your datasources and stuff, be sure to delete the generated stuff once you fixed everything

2 Likes
6

THAT WAS MY MISTAKE. Now I understand what happened. I started cleaning up from the reset made way back at first install without knowing that it is till in use as I did not change the System User Source nor the System Identity Provider that were still set to use the "temp" user source containing the same user.

2 Likes