5
Hi All,
We have just moved to an full web client environment of BC18 hosted in Azure.
One SQL server and an applications server.
We have no trouble logging into the webclient but when working in the client, users get the something went wrong message.
The only way to resolve this is to clear the history browser.
Any thoughts about this?
Reagrds,
Dimitri
Hello,
The token may expire at some point but it could also be that sessions are not automatically stopped which can be an issue. We hardly get support tickets about this topic anymore when setting it to 8 - 9. 8hrs should usually be sufficient. So a good analysis of the current behavior where users indeed logoff and logon again within that time range is the first advice. If the issue still occurs, feel free to raise is to Microsoft CSS via your partner or CSP so we can take a look together.
Thanks.
Thanks for this tip,..
I will change het life time and instruct the users to logoff.
Is this a know issue when working with Azure authentication?
Hello,
Please increase it to either 9 - 12 and have the users remember to logoff their sessions when they are done with their daily job.
Thanks.
Hi Inge,
Arround the time of the errors there are events with the:
The Saml2SecurityToken is rejected because the SAML2:Assertion's NotOnOrAfter condition is not satisfied. error.
I did allready changed the Extende Security Token Lifetime to 8
I forgot to mention we are using BC18 with Office 365 Authentification.
Gr,
Dimitri
I think i would start by checking the event log on the application server. That might give you some clue about what the root cause of this is.
#1
Sohail Ahmed
2,655
#2
Mansi Soni
1,574
#3
YUN ZHU
1,453
Super User 2025 Season 1
Share
Report
All responses (
Answers (
