question

Upvotes
Accepted
3 0 0 0

Open Dacs LOGOUT FORCED

We are seeing "LOG_OUT_FORCED" callback event on the first dacs destribution after monthly On-demand concurrent login roll-over. Do we need to try to relogin for this case ?

DACSopen-dacs
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
Accepted
7.6k 15 6 9

@tsuyoshi.inoue

I think you can treat this case like the logout case. If the user still valid and available on the DACS station, the re-login should be successful.


icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
3 0 0 0

@moragodkrit.chumsri_1 Thank you for your reply. I have also checked ADS's behavior

 DACS Trace is enabled by administrator.
 DACS Flush: Flushing the usage log.
 DACS Flush: Flushing the usage log.
 ==>> DACS execute: Activity on the DACS socket. Calling handler.
 DACS ReverifyLogin: The user 1 : xxxxxis being reverified.
 <<== DACS execute: Returned from handler.
 ==>> DACS execute: Activity on the DACS socket. Calling handler.
 DACS ReloginUserPass: The user 1 : xxxxx has passed DACS during a reLogin.
 DACS ForceRepermission: The user 1 : xxxxx is being repermissioned.
 <<== DACS execute: Returned from handler.
 DACS Item Permission SUCCESS: .N225 MARKET_PRICE
 DACS Flush: Flushing the usage log.
 DACS Trace is disabled by administrator.

ADS is doing "relogin" for this event . So our apps should do "relogin" also
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.