Not able to Login to the External portal from India and the same is Working fine from Other Countries Like US and Philippines
Not able to Login to the External portal from India and the same is Working fine from Other Countries Like US and Philippines.
If I set the pyDefaultTimeZone to null then it is working fine in India. Could see there is parameter TimezoneOffset with value Etc/GMT+5.5 is coming from the Authentication Service (Could see this parameter at the first step of the Authentication Activity) and setting this value to the pyDefaultTimeZone property of Operator page. So now the Operator.pyDefaultTimeZone = "Etc/GMT+5.5" which is throwing warning as below and causing the issue.
Warning: Operator.pyDefaultTimeZone 1.(Data-Admin-Operator-ID)PropertyInfo-EditValidate pyDefaultTimeZone timeZoneID
Can you please help me on this issue and how come the same is working from other regions ?
Accepted Solution
Pegasystems Inc.
US
When I look at the time zone field on the Operator ID form, I do not see Etc/GMT+5.5 listed in the dropdown. Can you use one of the values that is present in the list?
Pegasystems Inc.
US
What is the value of the TimezoneOffset parameter and pyDefaultTimeZone property when it works for other regions?
Pegasystems Inc.
IN
Hi Carissa,
For the Philippines/Manilia its coming as Etc/GMT+8 for both pyDefaultTimeZone property and TimezoneOffset parameter. Where as for me India/Hyderabad its coming as TimezoneOffset as Etc/GMT+5.5 and pyDefaultTimeZone property as America/New_York.
And I did not set the Timezone field in Operator record it is set to Select...
Accepted Solution
Pegasystems Inc.
US
When I look at the time zone field on the Operator ID form, I do not see Etc/GMT+5.5 listed in the dropdown. Can you use one of the values that is present in the list?
Pegasystems Inc.
IN
Hi,
It will work, but we can't hard code timezone value right ? How come the timezone value is very different for the specific to India. Do we need to do any modifications at server level ?
Pegasystems Inc.
IN
Hi,
If I put any value which is listed in the Time zone drop down, it is working fine without any issue. As I said in earlier post the TimezoneOffset parameter is populating at the Authentication Service activity which is copied to the pyDefaultTimeZone property which is causing issue.
The issue is clear the TimezoneOffset parameter(Etc/GMT+5.5) from Authentication activity is causing the issue if we set it to pyDefaultTimeZone property for India.
My Question is how come the TimezoneOffset is different for different regions ? Does this timezone is from Server or from Browser requestor ?
Pegasystems Inc.
PL
Also, Could you please trace and see what you will get in logs? I believe that it should be more details there on that problem.
Regards,
Jakub
Pegasystems Inc.
IN
Hi,
I did not see any error in logs until I set TimezoneOffset parameter is populating from the Authentication Service activity to the pyDefaultTimeZone property which is causing issue.
The issue is clear the TimezoneOffset parameter(Etc/GMT+5.5) from Authentication activity is causing the issue if we set it to pyDefaultTimeZone property for India.
My Question is how come the TimezoneOffset is different for different regions ? Does this timezone is from Server or from Browser requestor ?