Issue Details:-
EBS iHelp page issue, when user clicks on help page, it is prompting for credentials, which not a normal behaviour.
Once we pass the credentials, it suppose to take that to help page, but it is going to users home page.
Environment Details:
We have one dbTier and two appTiers and login is load balanced url.
Solution:
We reviewd below metalink document, but that didn't help us.
R12: iHelp Not Working After Implementing A Hardware Load Balancer, SSL Acceleration, Or DMZ (Doc ID 728463.1)
Worked with Oracle Support, and they found that the issue occurred due to hardware load balancer implementation. Oracle recommended to keep NULL for HELP_WEB_AGENT in the $CONTEXT_FILE and run autoconfig.
<HELP_WEB_AGENT oa_var="s_help_web_agent">https://myerp.domain.com</HELP_WEB_AGENT>
To
<HELP_WEB_AGENT oa_var="s_help_web_agent"></HELP_WEB_AGENT>
Run Autoconfig.
This fixed our issue and able to launch help page without prompting for username and password.
EBS iHelp page issue, when user clicks on help page, it is prompting for credentials, which not a normal behaviour.
Once we pass the credentials, it suppose to take that to help page, but it is going to users home page.
Environment Details:
We have one dbTier and two appTiers and login is load balanced url.
Solution:
We reviewd below metalink document, but that didn't help us.
R12: iHelp Not Working After Implementing A Hardware Load Balancer, SSL Acceleration, Or DMZ (Doc ID 728463.1)
Worked with Oracle Support, and they found that the issue occurred due to hardware load balancer implementation. Oracle recommended to keep NULL for HELP_WEB_AGENT in the $CONTEXT_FILE and run autoconfig.
<HELP_WEB_AGENT oa_var="s_help_web_agent">https://myerp.domain.com</HELP_WEB_AGENT>
To
<HELP_WEB_AGENT oa_var="s_help_web_agent"></HELP_WEB_AGENT>
Run Autoconfig.
This fixed our issue and able to launch help page without prompting for username and password.
No comments:
Post a Comment