New article
Recently updated
Ideagen Internal Audit (Aura): "A valid user could not be found matching the identity" - but then the wrong username is specified
The Scenario
- The organisation has two Windows domains, AAA.com and BBB.com
- There is a trust between the domains
- AAA.com contains the Pentana application server
- The user 'jsmith' has an account in each domain
- The user is set up in Ideagen Internal Audit (Aura) with an identity of BBB\jsmith
- The user is logged to their PC as BBB\jsmith
- Ideagen Internal Audit (Aura) does not let them log in, giving the error:
A valid user could not be found matching the identity AAA\jsmith
In other words, they are logged into their PC with their BBB account, Ideagen Internal Audit (Aura) is set up to allow access to BBB\jsmith, but Pentana is trying to use AAA\jsmith for authentication.
The Cause
Windows' cached credentials feature stores login details so that users don't have to re-enter them each time they access a server. In the scenario above:
- The user accesses the Ideagen Internal Audit (Aura) server (for example to download the ClickOnce package) and is prompted for their username and password
- User logs in as AAA\jsmith
- Their credentials are stored in Windows Credential Manager to be used the next time they access that server
- User starts Pentana, which uses the credentials that are cached
Resolution
To fix this, delete the incorrect cached credentials:
- Click Start and go to Windows System\Control Panel\User Accounts\Credential Manager
- Select Windows Credentials
- Locate the server in the list, and click on it to expand
- Click Remove