Re: Strange date behavior in SSO environment
Henry, I already found that KB. But that only describes the way it should work. I still have the problem that user who access my ARS application from a timezone like +5,5 see the same timestamp (e.g. 'modified time') in the result list and the detail view with 1 hour difference. BMC support (IssueID:ISS03006251) seems not very eager to validate or fix this problem... Jörg -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Douglas, Henry Sent: Friday, March 30, 2007 3:20 PM To: arslist@ARSLIST.ORG Subject: Re: Strange date behavior in SSO environment ** Just so happen to be looking into that same issue. Here's the KB# from BMC 24869. Hope this helps. Henry Douglas From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Steinigans-Hillemann, Joerg Sent: Thursday, March 29, 2007 1:58 AM To: arslist@ARSLIST.ORG Subject: Re: Strange date behavior in SSO environment Hi List, since there was no answer to my question, can I assume that no one else has this problem within a SSO environment? Best regards, Joerg -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Steinigans-Hillemann, Joerg Sent: Friday, March 23, 2007 9:24 AM To: arslist@ARSLIST.ORG Subject: Strange date behavior in SSO environment ** Hi List, has anyone else seen the following behavior (Mid-Tier 6.3 Patch 14)? Support told me that problem would be solved with patch 20, but it isn't solved. The problem with SSO is, that the timezone of the local computer cannot be determined. So the entry in the User-Preferences Form is always used. The scenario is: The entry in the User-Preferences Form is set to e.g. Europe/London The local windows timezone configuration is set to something uneven (no full hour), e.g. GMT +6:30 Rangun or GMT +5:30 or ... Now open any Form and do a query. The result is, that there is a 1 hour difference between a date field in the result list and the same field in the detail view. The SSO behavior can be simulated by disabling the timezone detemination in the login.jsp and the login_common.jsp. ( In the login.jsp delete the line input type=hidden name=timezone value= ) ( In the login_common.jsp comment out the line this.document.loginForm.timezone.value=getTimezone(); ) Mit freundlichen Grüßen / Best regards Jörg Steinigans-Hillemann KEYMILE GmbH __20060125___This posting was submitted with HTML in it___ STATEMENT OF CONFIDENTIALITY: The information contained in this message or any attachments to this message are intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material as well as being protected from disclosure. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is strictly prohibited. If you received this in error, please contact the sender immediately and delete the material from any computer. __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are
Re: Strange date behavior in SSO environment
Just so happen to be looking into that same issue. Here's the KB# from BMC 24869. Hope this helps. Henry Douglas From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Steinigans-Hillemann, Joerg Sent: Thursday, March 29, 2007 1:58 AM To: arslist@ARSLIST.ORG Subject: Re: Strange date behavior in SSO environment Hi List, since there was no answer to my question, can I assume that no one else has this problem within a SSO environment? Best regards, Joerg -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Steinigans-Hillemann, Joerg Sent: Friday, March 23, 2007 9:24 AM To: arslist@ARSLIST.ORG Subject: Strange date behavior in SSO environment ** Hi List, has anyone else seen the following behavior (Mid-Tier 6.3 Patch 14)? Support told me that problem would be solved with patch 20, but it isn't solved. The problem with SSO is, that the timezone of the local computer cannot be determined. So the entry in the User-Preferences Form is always used. The scenario is: The entry in the User-Preferences Form is set to e.g. Europe/London The local windows timezone configuration is set to something uneven (no full hour), e.g. GMT +6:30 Rangun or GMT +5:30 or ... Now open any Form and do a query. The result is, that there is a 1 hour difference between a date field in the result list and the same field in the detail view. The SSO behavior can be simulated by disabling the timezone detemination in the login.jsp and the login_common.jsp. ( In the login.jsp delete the line input type=hidden name=timezone value= ) ( In the login_common.jsp comment out the line this.document.loginForm.timezone.value=getTimezone(); ) Mit freundlichen Grüßen / Best regards Jörg Steinigans-Hillemann KEYMILE GmbH __20060125___This posting was submitted with HTML in it___ __20060125___This posting was submitted with HTML in it___ STATEMENT OF CONFIDENTIALITY: The information contained in this message or any attachments to this message are intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material as well as being protected from disclosure. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is strictly prohibited. If you received this in error, please contact the sender immediately and delete the material from any computer. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are
Re: Strange date behavior in SSO environment
Hi List, since there was no answer to my question, can I assume that no one else has this problem within a SSO environment? Best regards, Joerg -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Steinigans-Hillemann, Joerg Sent: Friday, March 23, 2007 9:24 AM To: arslist@ARSLIST.ORG Subject: Strange date behavior in SSO environment ** Hi List, has anyone else seen the following behavior (Mid-Tier 6.3 Patch 14)? Support told me that problem would be solved with patch 20, but it isn't solved. The problem with SSO is, that the timezone of the local computer cannot be determined. So the entry in the User-Preferences Form is always used. The scenario is: The entry in the User-Preferences Form is set to e.g. Europe/London The local windows timezone configuration is set to something uneven (no full hour), e.g. GMT +6:30 Rangun or GMT +5:30 or ... Now open any Form and do a query. The result is, that there is a 1 hour difference between a date field in the result list and the same field in the detail view. The SSO behavior can be simulated by disabling the timezone detemination in the login.jsp and the login_common.jsp. ( In the login.jsp delete the line input type=hidden name=timezone value= ) ( In the login_common.jsp comment out the line this.document.loginForm.timezone.value=getTimezone(); ) Mit freundlichen Grüßen / Best regards Jörg Steinigans-Hillemann KEYMILE GmbH __20060125___This posting was submitted with HTML in it___ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are
Strange date behavior in SSO environment
Hi List, has anyone else seen the following behavior (Mid-Tier 6.3 Patch 14)? Support told me that problem would be solved with patch 20, but it isn't solved. The problem with SSO is, that the timezone of the local computer cannot be determined. So the entry in the User-Preferences Form is always used. The scenario is: The entry in the User-Preferences Form is set to e.g. Europe/London The local windows timezone configuration is set to something uneven (no full hour), e.g. GMT +6:30 Rangun or GMT +5:30 or ... Now open any Form and do a query. The result is, that there is a 1 hour difference between a date field in the result list and the same field in the detail view. The SSO behavior can be simulated by disabling the timezone detemination in the login.jsp and the login_common.jsp. ( In the login.jsp delete the line input type=hidden name=timezone value= ) ( In the login_common.jsp comment out the line this.document.loginForm.timezone.value=getTimezone(); ) Mit freundlichen Grüßen / Best regards Jörg Steinigans-Hillemann KEYMILE GmbH ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are
