moscow timezone

[AlekseyMakarov]

hello

i have RSA am 8.2 sp1 4, and have trouble with time zone.

in Operation Console -> Administration - > date & time - Moscow have timezone +4 (but in real world Moscow timezone +3)

Tnx.

[_EricaChalfin]

1b2yJeUmmmSiy1A7EBabVQtx6AhtCNBidhZ5be4KRyM=‌,

I've moved your question to the https://community.rsa.com/community/products/securid?sr=search&searchId=1b9c3561-0c03-48ee-b374-a48b11f5cbd3&searchIndex=0‌ space so you can get an answer to your question.

Regards,

Erica

[_EricaChalfin · Accepted solution]

Aleksey Makarov‌,

From the Operations Console I see that Moscow has the value of UTC +4, as shown:

     

As you mentioned, Moscow should have a  value of UTC +3, as per MSK – Moscow Standard Time (Time Zone Abbreviation) and Wikipedia's map of standard world time zones.

In order to correct the value in the  Authentication Manager Operations Console UI, you will need to Contact RSA Customer Support and have a support engineer log a product defect.  

Regards,

Erica

[EdwardDavis]

For now, pick Europe/Moscow, and even though the selector in the Ops Console shows +4, it

will set the correct local time on the RSA Server as MSK and that will have the correct +3 offset.

edavis-vm150:~ # date
Wed Sep 6 14:27:54 EDT 2017
edavis-vm150:~ # date -u
Wed Sep 6 18:27:56 UTC 2017

after change to Europe/Moscow

edavis-vm150:~ # date
Wed Sep 6 21:29:57 MSK 2017
edavis-vm150:~ # date -u
Wed Sep 6 18:30:01 UTC 2017

Actual Moscow time checked with an independent source is 
21:30 PM
Wednesday, September 6, 2017 (GMT+3)
Time in Moscow, Russia

so....choosing Moscow +4 really does set  Moscow +3 

I created a defect AM-31421 so that this +4 can be corrected.

[_EricaChalfin]

Thanks, pFAX8dqXawUTDxZ4I3nhT1XEt83rjtLgTslU9FLYwZU=‌!

Regards,

Erica