OAM 11g - webgate redirect loop

Have you ever run into a problem where you have an infinite redirect loop between the OAM server and a webgate?

If so, the first thing to do is CHECK THE TIME on both the webgate and oam hosts!

If the time is out of sync the webgate will think the OAM token has expired - redirecting you back again to the OAM server, who will happily generate another "new" (but expired) token and send you back to the webgate. Rinse and repeat....

Post a Comment

Popular posts from this blog

OAM R2 REST APIs for Policy Management

SAML Federation in OAM 11g R2

Apache reverse proxy with LDAP authentication