ddgaikwad Absent Member.
Absent Member.
329 views

Bacb button does not work in browser when logged in via NAM


Hi All,

I think this is working as per design, but needed a second thought on
it.
We have SharePoint and OBIEE applications protected via NAM.

Now when a user logs in to these application via NAM, they are not able
to navigate back to the previous page using the Back button in the
browser.
They are greeted with a session expired page... I think this is normal
when you are using a https connection.

Could you please provide me with you second thoughts?
Is this some we can fix or is it working as per design?

Thank you,


--
ddgaikwad
------------------------------------------------------------------------
ddgaikwad's Profile: https://forums.netiq.com/member.php?userid=5917
View this thread: https://forums.netiq.com/showthread.php?t=53865

0 Likes
5 Replies
ddgaikwad Absent Member.
Absent Member.

Re: Bacb button does not work in browser when logged in via NAM


Guys, any insight on this one?
Is this something which could be solved by increasing the session
timeout from within NAM?
Do we have such a setting?

Thank you!


--
ddgaikwad
------------------------------------------------------------------------
ddgaikwad's Profile: https://forums.netiq.com/member.php?userid=5917
View this thread: https://forums.netiq.com/showthread.php?t=53865

0 Likes
Knowledge Partner
Knowledge Partner

Re: Bacb button does not work in browser when logged in via NAM

ddgaikwad wrote:

>
> Hi All,
>
> I think this is working as per design, but needed a second thought on
> it.
> We have SharePoint and OBIEE applications protected via NAM.
>
> Now when a user logs in to these application via NAM, they are not able
> to navigate back to the previous page using the Back button in the
> browser.
> They are greeted with a session expired page... I think this is normal
> when you are using a https connection.
>
> Could you please provide me with you second thoughts?
> Is this some we can fix or is it working as per design?



There could be a whole host of different reasons.

many sites implement anti-CSRF functionality (which when implemented incorrectly can often break the back button)
a URL that isn't rewritten in a script for example could cause problems.
Potentially cookie-mangling if you have that enabled.


Without more details, it is hard to give you a better answer
Alex McHugh - Knowledge Partner - Stavanger, Norway
Who are the Knowledge Partners
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
ddgaikwad Absent Member.
Absent Member.

Re: Bacb button does not work in browser when logged in via NAM


That's interesting.
Ok, what are the others do we need to dig this further?


--
ddgaikwad
------------------------------------------------------------------------
ddgaikwad's Profile: https://forums.netiq.com/member.php?userid=5917
View this thread: https://forums.netiq.com/showthread.php?t=53865

0 Likes
ddgaikwad Absent Member.
Absent Member.

Re: Bacb button does not work in browser when logged in via NAM


ddgaikwad;258903 Wrote:
> That's interesting.
> Ok, what are the others do we need to dig this further?


There is one more thing I would like to put here is that:
1. There is no browser caching enabled for this proxy.
2. This proxy is running on port 80, does this make any difference?
3. Could it be possible that he backend server is running on SSL and
this is not could cause the issue of back button not working?


--
ddgaikwad
------------------------------------------------------------------------
ddgaikwad's Profile: https://forums.netiq.com/member.php?userid=5917
View this thread: https://forums.netiq.com/showthread.php?t=53865

0 Likes
Knowledge Partner
Knowledge Partner

Re: Bacb button does not work in browser when logged in via NAM


ddgaikwad;258838 Wrote:
> Hi All,
>
> I think this is working as per design, but needed a second thought on
> it.
> We have SharePoint and OBIEE applications protected via NAM.
>
> Now when a user logs in to these application via NAM, they are not able
> to navigate back to the previous page using the Back button in the
> browser.
> They are greeted with a session expired page... I think this is normal
> when you are using a https connection.
>
> Could you please provide me with you second thoughts?
> Is this some we can fix or is it working as per design?
>
> Thank you,


What happens if you access the origin server directly?
We have lots of apps that don't work correctly if the back-button is
used, even when we do not front-end with NAM. It's not uncommon.
We just tell people (or the vendors own documentation states do not use
the back button) to not use the back button.

For example, Novell says in ZCM, when using the ZCC to not use the back
button. If you use it "too many times" it throws java errors.
In our IBM Websphere Portal, if you try to use the back button you'll
almost always get session expired info because WebSphere Portal (at
least the old version we are on) has unique session strings that compose
the URL and when you click back, it tries to use the funky
number/session info that is expired.

So we tell people to not use the back button.


--
kjhurni
------------------------------------------------------------------------
kjhurni's Profile: https://forums.netiq.com/member.php?userid=322
View this thread: https://forums.netiq.com/showthread.php?t=53865

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.