API Support Forum
OEC API > API Support > GFAPI COM Forced Login Not Working
Author Topic: GFAPI COM Forced Login Not Working
(7 messages, Page 1 of 1)
Moderators: VPfau
RWare2020
Posts: 205
Joined: Feb 11, 2020


Posted: Jul 08, 2022 @ 04:12 PM             Msg. 1 of 7
It appears that the forced login is not working for the GF API COM.

I have tried both WithForcedLogin and WithForcedLogin_2 to see if one would work and not the other, but neither of them work. When someone logs into the same user with the same UUID, it immediately disconnects the second instance with a message of "UserAlreadyLoggedIn".

Am I doing this correct? OECAPI just works without having to specify a force login.

Thanks.
JSmith5611
Posts: 187
Joined:


Posted: Jul 13, 2022 @ 08:04 AM             Msg. 2 of 7
Here's how it should be working:

without force login:
Instance 1 logs in.
Instance 2 attempts to log in, but fails.

with force login:
instance 1 logs in.
instance 2 attempts to log in.
instance 2 succeedes
instance 1 is disconnected.

In no situation should both instances be connected with the same user.

Is this not what you're seeing?
Jason Smith
RWare2020
Posts: 205
Joined: Feb 11, 2020


Posted: Jul 13, 2022 @ 11:06 AM             Msg. 3 of 7
This is not what I am seeing. This is what I am seeing with forced login:

instance 1 logs in.
instance 2 attempts to log in.
instance 2 is disconnected with "user already logged in" message
instance 1 remains connected.
JSmith5611
Posts: 187
Joined:


Posted: Jul 13, 2022 @ 11:37 AM             Msg. 4 of 7
Can you pm me your user name and which environment you see this behavior? I'd like to check logs.
Jason Smith
RWare2020
Posts: 205
Joined: Feb 11, 2020


Posted: Jul 13, 2022 @ 11:40 AM             Msg. 5 of 7
Thanks, I sent that over.
JSmith5611
Posts: 187
Joined:


Posted: Jul 15, 2022 @ 08:36 AM             Msg. 6 of 7
Please check your PMs, i sent a log analysis over (didn't post here since it contained IPs)
Jason Smith
RWare2020
Posts: 205
Joined: Feb 11, 2020


Posted: Jul 15, 2022 @ 12:19 PM             Msg. 7 of 7
Your response was correct, it was an issue with my reconnecting code.

Thank you.