Google Search Appliance (GSA) Crawler Does not Redirect to Protected Resource After Oracle Access Manager 11g (OAM) Authentication/Authorization
(Doc ID 2218664.1)
Last updated on SEPTEMBER 02, 2021
Applies to:Oracle Access Manager - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
GSA is being redirected to the OAM server, but not being sent back to the content server after authentication/authorization.
This is causing the Search appliance to recognize the redirected URL as "excluded - not part of crawl pattern".
Authenticating/authorizing is occurring, but cannot index the content.
- url_before_redirects: http://<CONTENT_SERVER_HOST>/<URI>?
- url_after_redirects: http://<OAM_SERVER_HOST>/oam/CredCollectServlet/WNA?bmctx=<VALUE>&spnegotoken=string&challenge_url=/oam/CredCollectServlet/WNA&request_id=<REQUEST_ID>&authn_try_count=0&locale=en_US&resource_url=http://<CONTENT_SERVER_HOST>/<URI>
- Why is the crawler not being redirected back to the content server URL?
- Is this the expected behavior?
- Can we redirect the crawler back to the original content servers URL after authentication/authorization?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document