“Error: Single Sign Off didn’t take place” while logging out of OAM Admin console

I have logged into OAM 11g Admin console as weblogic user and performed some operations such as Creating Agents etc., and clicked logout. It redirected to the page showing “Sign off did not place”.

See the below screenshot for complete error message.      

Notice the URL it is redirected to OAM_HOST:port/oamsso/logout.html?end_url=/oamconsole/faces/pages/PolicyManager.jspx.

The IDMDomainAgent is the webgate name which protects OAM application deployed on WebLogic server. This webgate will be provided during OAM installation and configuration phase. I have logged into OAM console once again to see the status of IDMDomainAgent status and it is enabled.

I have checked the OAM diagnostics log at $WL_DOMAIN/servers/oam_server_instance/logs/oam-server1-diagnostics.log and found an error message “Failed to communicate with any of configured Access Server, ensure that it is up and running” but could see that OAM WebLogic instance is up and running. So I have bounced the OAM managed server once and I am able to logout of OAM console succesfully.

 

 

About the Author Mahendra

I am engulfed in Oracle Identity & Access Management domain. I have expertise on providing the optimized solutions for user provisioning, web access management, Single Sign-On and federation capabilities etc., I am also well versed with complex integrations within Identity Management and other product domains. I have expertise on building demos and implementation experience on products Oracle Access Manager, Oracle Adaptive Access Manager, Oracle Entitlement Server, Oracle Virtual Directory, Oracle Internet Directory etc., Look @ my blog: http://talkidentity.blogspot.com

Leave a Comment:

11 comments
Naj says October 1, 2012

Hi,

I Installed OID 11.1.1.6,OAM 11.1.1.5(Without SOA) in diffrent domain in same weblogic server (OID AD SYNC is success) now when i am login in to OAM the managed server named
oam_server1 is in shutdown mode and am not able to make it up. How to make it up.

OAM Domain Admin server diagnostics i could see some error ([APP: FMW Welcome Page Application#11.1.0.0.0] Failed to communicate with any of configured Access Server, ensure that it is up and running.)

1) is it necessary to have a managed server
in OAM.
2) Before Installing Forms i would like to
test oam with AD users.How can i do this.
3) How will i install Forms 11g on the same
server and configure with the OAM.

Reply
Mahendra says October 1, 2012

Naj,

Yes, you would need to bring up OAM managed server to access OAM console. If you are nto able to bring up OAM managed server, then what errors do you see in logs?

OAM managed server is a must in OAM env. You can test OAM login against AD by creating identity store in OAM console and making it as system store. Make sure to have admin group created in AD and assign some users for OAM admin login purposes.

Reply
Naj says October 1, 2012

@ mahendra
thanks for your quick replay,yes i have done all these steps and am able to login with Administrator group users.till this everything is fine but when i check the oam managed server is not up , also i would like to know some tips installing forms 11g in the same server.
1)on the same weblogic server with diffrent domain is possible.
2) do i need to install separate weblogic and domain.

Reply
Mahendra says October 2, 2012

Naj,

Please tell us the errors you see in OAM managed server logs. OAM manager server has to be up and running to use OAM console.

I am not a Forms11g expert.

-Mahendra.

Reply
mibdah says October 11, 2012

I Installed OID 11.1.1.6,OAM 11.1.1.5(Without SOA)
When I start OAM with command :
startManagedWebLogic.sh oam_server1 http://localhost:7001

It fails with ”
Failed to communicate with any of configured Access Server, ensure that it is up and running”

Reply
Mahendra says October 16, 2012

mibdah ,

Please confirm if OAM server is started or not? You may get this message while starting WebLogic Admin server but can be ignored.

If OAM server is not started, what is the exception you see in logs?

Reply
User says October 17, 2012

Is it ok to get this error in Admin Server every time you click a link on oam console:

Failed to communicate with any of configured Access Server, ensure that it is up and running

oam server should be running on 14100 but when i try to telnet to that server on 14100 it says connection refused. telnet works for 5575 though.

Is this the expected behavior?

Reply
Pratima says October 17, 2012

Is it ok to get this error in Admin Server every time you click a link on oam console:

Failed to communicate with any of configured Access Server, ensure that it is up and running

oam server should be running on 14100 but when i try to telnet to that server on 14100 it says connection refused. telnet works for 5575 though.

Is this the expected behavior?

Reply
Mahendra says October 17, 2012

No, this error will not pop up if OAM server is up. 5575 is the proxy port and this is fine. Login to Admin console and check the deployments for OAM console application.

Also check for the servers in Admin server to find ports.

Reply
pratima says October 18, 2012

Servers in admin server are running on 14100. Deployments look fine as well. So, you mean that we should be able to telnet to oam server on 14100? I can login to admin console, create policies, register agents etc.
just that I can’t telnet to server on port 14100 which says something is wrong.

Reply
moulali says November 20, 2012

hi,
i have installed 64bit weblogic 10.3.5,JDK 1.6.0_35 and oam 11.1.1.5.0. but i am unable to access oamconsole when oam server is up, but i can access it when oam server is down.i have checked the oam_server.log file oam server is started in running mode but in between there is an error, i.e
java.lang.NoClassDefFoundError: Could not initialize class oracle.dfw.impl.common.TempFileManager
at oracle.dfw.spi.portable.PortableDiagnosticsFrameworkProvider.init(PortableDiagnosticsFrameworkProvider.java:120)
at oracle.dfw.framework.DiagnosticsFramework.initializeProvider(DiagnosticsFramework.java:98)
at oracle.dfw.framework.DiagnosticsFramework.(DiagnosticsFramework.java:53)
at oracle.dms.wls.DMSStartup.start(DMSStartup.java:212)
at oracle.dms.wls.DMSStartup.startUp(DMSStartup.java:118)
at oracle.dms.wls.DMSStartup.main(DMSStartup.java:67)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)

at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeMain(ClassDeploymentManager.java:362)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClass(ClassDeploymentManager.java:272)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.access$000(ClassDeploymentManager.java:54)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager$1.run(ClassDeploymentManager.java:214)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.invokeClassDeployment(ClassDeploymentManager.java:207)
at weblogic.management.deploy.classdeployment.ClassDeploymentManager.runStartupsBeforeAppDeployments(ClassDeploymentManager.java:149)
at weblogic.management.deploy.classdeployment.ClassDeploymentService.start(ClassDeploymentService.java:20)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
#### <>

#### <>
…..

please help me get out of this error.
thanks in advance.

Reply
Add Your Reply

Not found