This content has been marked as final. Show 8 replies
To fix this issue, do the below.
1) Login to weblogic console of OAM domain.
2) Click on Lock & Edit
3) Navigate to Summary of Security Realms >myrealm >Providers.
4) Select IAMSuiteAgent
5) Delete it.
6) Save & Activate the changes.
7) Restart Admin and OAM servers.
You should be able to login to oam console now. You need to make sure LDAP scheme is your OID identity store under Access Manager Settings --> Authentiction Modules --> LDAP Authentication Module --> LDAP.
Just wanted to understand the use of this IAMSuiteAgent, since I have deleted this it is working fine. But can you throw some light on the impact without the IAMSuiteAgent?
Is this created automatically on some activity on the OAM console? or it comes by default when installed?
This information would be very helpful for me. Thanks in advance.
It is created automatically at the time of installation of Oracle Access Manager.
Check this link for detail about IAMSuiteAgent.
Yes, what user 903181 said is correct.
Actually, we will have an agent with the name IAMSUITEAGENT IN OAMCONSOLE and there will be a provider in weblogic name with the same name. We just deleted provider from weblogic and the agent still be there in OAMconsole which will be used for registration and for resource protection.
Even if you take a look on oracle docs, deleting IAMSUITEAGENT is one of the step.
So, you should be good.