nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Redirecting user from login screen

tsatt

Hi All,

I have a cgi script that runs through a custom menu item in TeamSite.
When the user clicks the custom menu item, I want to be able to send the user to the TeamSite login screen and then back to the custom cgi after authentication if the user cookie is not set.

Does anyone have any thoughts how this can be done?

Thanks

TeamSite 6.5
Solaris 8

Find more posts tagged with

Comments

ISCBorisB

Hi All,

I have a cgi script that runs through a custom menu item in TeamSite.
When the user clicks the custom menu item, I want to be able to send the user to the TeamSite login screen and then back to the custom cgi after authentication if the user cookie is not set.

Does anyone have any thoughts how this can be done?

Thanks

TeamSite 6.5
Solaris 8

If the user is not logged into TS he won't be able to to click a Menu Item - or do anything else for that matter until he
logs in. Conversely, if he is logged in there is an active IWAUTH cookie and there is no need to re-send him to login.
What's your beef?

TestReportDesign.rptdesign

TestLibrary.zip

tsatt

My beef is: Smiley Happy

1. Sometimes the user clears cookies after he/she is logged in due to any reason. In such case, the user will need to log in. In the cgi I am reading the iw_user cookie to get the user id. we control the access to custom menu items for diff custom commands and custom reports for diff users.

2. Some users only use IE. In case if the user ends up opening the url in Firefox (may be he/she defaulted the browser to IE), the cookie wont be there.

Alternatively, if the user does not have the cookie set, I am showing them a message and asking them to log in to TeamSite. Since the error came from Firefox, chances are that the user might still go to IE to login and find that he/she is already logged in. I would like the user to be directed to the TeamSite login screen and let them authenticate themselves and then send them back to the cgi.

Thanks

ISCBorisB

My beef is:

1. Sometimes the user clears cookies after he/she is logged in due to any reason. In such case, the user will need to log in. In the cgi I am reading the iw_user cookie to get the user id. we control the access to custom menu items for diff custom commands and custom reports for diff users.

2. Some users only use IE. In case if the user ends up opening the url in Firefox (may be he/she defaulted the browser to IE), the cookie wont be there.

Alternatively, if the user does not have the cookie set, I am showing them a message and asking them to log in to TeamSite. Since the error came from Firefox, chances are that the user might still go to IE to login and find that he/she is already logged in. I would like the user to be directed to the TeamSite login screen and let them authenticate themselves and then send them back to the cgi.

Thanks

Frankly, I find this "same TS Session alternating Browsers" idea a bit absurd. Also, if the User cleans-up cookies
within session - tough luck, let TS handle it and force log-in when needed. In any case, how often does that happen?
May be it's just a matter of training and perhaps little Client Configuration? Btw, what is the information that you can get
from undocumented cookie but can not obtain by other means?

That said, you can try to play with few ideas in your CGI. Note that I'm speculating here, IMO it's a waste of efforts even
if you can make it work. For example, you can either pre-code or generate on the fly the Page(s) that only purpose
in life is to do two things:
1. force-expire IWAUTH cookie ( see for example [post=106887]this[/post] post ) and
2. Immediately redirect to TS Log-In URL ( change window.location or use http-equiv HTML Meta )

In your CGI you'll either use pre-canned Page as action and submit or simply generate / emit this Page.
Note that without unsupported hacks you probably won't be able to get right back to the menu Item from the Login Page.
Within the same idea you can perhaps try to redirect right back to the Menu Item CGI instead of Login with the assumption
that TS itself will force Login now that IWAUTH cookie is gone, etc...

Needless to say, none of that is documented or supported. Good luck.

tsatt

You know how the business owners are.... Smiley Very Happy

They want things to be done; does not matter how we do it. If something is not possible at all, then we need to tell them that it is not possible but before we say that we need to make sure that is the case or an alternate is not possible. Its good to keep business happy Smiley Wink

Anyways. Thanks for your suggestions. I will post something if I am able to do anything.