We know what this message means at the login page
But what does this mean on a login page
Isn't access related to specific resources, not your entire login? How can someone have valid creds but no access?
We know what this message means at the login page
But what does this mean on a login page
Isn't access related to specific resources, not your entire login? How can someone have valid creds but no access?
Do you have multiple repositories? Could the user be technically logging into a repository here that they don't have access to?
Just one repository. Can a user not have access to login but be licensed? Where is this setting? If we remove the license, they get the username or password is incorrect message.
I can sort of make this happen if an account is added to LFDS but not added to the repository itself in the Administration Console. In Web Client 11 and STS 12, at least, it opens a new page as if it's going to log me in before it shows me the 9013 error. Your screenshot looks like it might not be progressing out of the STS login page, so may be talking about something else.
Oh let me try adding them to Administration console too. Someone informed me years ago that there was no need to add them in 2 different places and I thought this was a more logical approach. When added in LFDS it was supposed to create their account in Admin Console after their first login.
The user account is automatically created in Admin Console on first login only if the user is a member of a trusted group already added to the Admin Console.
Windows and LFDS accounts need to be allowed login to log into a repository. That can happen either by directly adding them to the repository as a trusted account in the Admin Console or by being part of a group that was already trusted for login.
User account created in the repository are implicitly trusted for login to that repository because they only exist in that repository context.