Hello,
The errors/warns you outlined will not stop one from being able to Authenticate. There is a major difference between Authentication and Authorization.

Authentication for most customers is handled by OSP (some use Access Manager as the OAuth provider). OSP will look-up the user in eDirectory or Active Directory, if found update information on that user in the Identity Vault, create an OAuth token, and redirect back to Identity Governance, Identity Reporting, or External Workflow.

Authorization then happens at Identity Governance, Identity Reporting, or External Workflow. Meaning these modules/components then parse the OAuth Token and utilize that information to confirm if the Authenticated user is allowed to perform actions in their module/component. Based upon their look-up the user is the granted certain access rights or presented with a message outlining they are not authorized. If the user is unknown to the module/component, they can receive a message similar to:

Steven Williams is authenticated, but does not have any rights to this system. Please logout.

Questions:
1) When one tries to access Identity Governance, Identity Reporting, or External Workflow, are you redirected to the OSP Login page?

2) If yes #1, after providing an ID and Password do you receive message about invalid ID/Password OR are you redirected back to one (1) of the above applications and then receive a different message in the UI OR the page does not render?

3) Is OSP deployed on the same tomcat as Identity Governance?

4) Is OSP pointing to eDirectory or Active Directory for the Identity Vault?

Sincerely,
Steven Williams
Principal Enterprise Architect
OpenText Cybersecurity

Thanx for answering.

1) Yes - i'm redirected to OSP login page. And as it is a clean install,

2)  "Logon failed - try again" (translated from Swedish)  I'm trying to log on using the bottstrap account (from Active Directory - not from file)

3) Yes

4) Active Directory

Thanx for answering.

1) Yes - i'm redirected to OSP login page. And as it is a clean install,

2)  "Logon failed - try again" (translated from Swedish)  I'm trying to log on using the bottstrap account (from Active Directory - not from file)

3) Yes

4) Active Directory

Hello,

Most of the time when a customer outlines they are unable to Login when using Active Directory as the Identity Vault, it is because they did not extend the schema as outlined in the Installation Guide: https://www.microfocus.com/documentation/identity-governance/4.2/install-guide/b1iq4nvf.html#t4b64uo9k3m6 

In your set-up, I have a feeling that OSP is set to WARN for the logging level in the setenv.sh. If you change this to ALL, restart, and test again there will be more information. If I am correct about the above, in the osp log will be an error about not being able to write on the user in AD.  If that is the case, you need to extend the schema in your AD server.

Sincerely,
Steven Williams
Principal Enterprise Architect
OpenText Cybersecurity