Policy Agent 2.2 - Apache 2.0.54 / AM 7.1 - Sun appserver 9 -Sun DS 6 XP

hi all,

I have a policy agent installed on apache. Am is installed on the appserver.

Also installed is a CustomLoginModule.

When I want to access a protected page, the CustomLoginModule loginpage is displayed. When I supply the credentials authentication is successful, but the authentication for the agent fails. The agent profile exists in the root realm, and in the Directory. I also cannot log into the AM console with the agents credentials(user profile does not exists).

any tips ?

Thanks

[531 byte] By [amusera] at [2007-11-27 10:59:39]
# 1

What error are you seeing in the AM debug and AMAgent logs? More specifically, what is in amAuthApplication?

AaronAnderona at 2007-7-29 12:24:30 > top of Java-index,Web & Directory Servers,Directory Servers...
# 2

hi aaron,

thanks for the reply ...

In the amAuthApplication log I can see that the agent is successfully autherized.

'Internal Auth is successful : User = uid=UrlAccessAgent,ou=agents,dc=xxx,dc=xxx'

In the agent log is see the request/response xml, and in the response the agent gets back from AM :

"<LoginStatus status="failed"></LoginStatus><Exception message="User Requires Profile to Login" errorCode="100" templateName="login_denied.jsp"></Exception></Response>"

Also in amIdm log:

WARNING: Unable to check if identity is active agent::UrlAccessAgent in any configured data store

Message:Plug-in com.sun.identity.idm.plugins.ldapv3.LDAPv3Repo does not support operation read for type agent

at com.sun.identity.idm.plugins.ldapv3.LDAPv3Repo.isActive(LDAPv3Repo.java:842)

at com.sun.identity.idm.server.IdServicesImpl.isActive(IdServicesImpl.java:975)

.....

.....

but in LDAPv3Repo

LDAPv3Repo: getSupportedOps on IdType: agent called

supportedOps Map = {IdType: realm=[Operation: service, Operation: delete, Operation: edit, Operation: read, Operation: create], IdType: role=[Operation: delete, Operation: edit, Operation: read, Operation: create], IdType: filteredrole=[Operation: delete, Operation: edit, Operation: read, Operation: create], IdType: group=[Operation: delete, Operation: edit, Operation: read, Operation: create], IdType: user=[Operation: service, Operation: delete, Operation: edit, Operation: read, Operation: create], IdType: agent=[Operation: delete, Operation: edit, Operation: read, Operation: create]}

07/20/2007 02:49:12:718 AM NZST: Thread[httpWorkerThread-8080-1,10,Grizzly]

LDAPv3Repo: isActive called: type:IdType: agent; name:UrlAccessAgent

read for agent is configured!

amusera at 2007-7-29 12:24:30 > top of Java-index,Web & Directory Servers,Directory Servers...