Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Operation Completed Successfully #337

Closed
X-Jaber opened this issue Apr 16, 2024 · 1 comment
Closed

Operation Completed Successfully #337

X-Jaber opened this issue Apr 16, 2024 · 1 comment

Comments

@X-Jaber
Copy link

X-Jaber commented Apr 16, 2024

We have been facing this issue for a while now, unfortunately there weren’t much of resources online to help us resolve this issue,
I was wondering if it is familiar for you and it something you could help us with.

We found it was mentioned here issue #198
we could see it has been resolved in 3.1.2202.2 based on the change log but yet we are on a later release 3.1.2207.0v. and facing the same issue was this issue addressed in newer versions?

what happens?
when our users’ login enters the correct OTP code they get "Operation Completed Successfully " attached for reference,
and they have to enter the OTP multiple times until it works.

We have made a lot of restarts but we are not quite sure what is wrong and where to start troubleshooting this issue

image

@redhook62
Copy link
Member

Hi @X-Jaber

I validated your configuration and it is correct.

I have no precise idea of your problem, because I have never been able to notice it.

This type of error comes from a Win32 call, we have very few in our code.
this can come from your operating system.
These Win32 calls are in no way used during the authentication process you describe.

The easiest thing is for you to test the latest version, it won't be any worse.
Can you give us feedback on the latest version ?

I am moving this issue to discussion, because the people who had this problem may also be able to help you.

regards

@neos-sdi neos-sdi locked and limited conversation to collaborators Apr 16, 2024
@redhook62 redhook62 converted this issue into discussion #338 Apr 16, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants