Problem  refers to: email owa via oauth2

Solving a problem from 2 years ago to version 6.3.4 community.microfocus.com/.../6-3-4-upgrade-fails-to-authenticate-to-filr

doesn't work because we don't have such paths.

Hello Pawel,

Can you check the Authenticators Management event, if the option Return groups on logon is Off? Set it to ON and see what happens?

If this doesn't help please open a service request ticket with Support, so they can ask for logs and analyze this further in detail. It may need more than a forum interaction.

Thanks.

Regards,

Luciano Testa

Hi Thank you for your interest in problem. Switching the parameter did not solve the problem. Probably the thread from two years ago is a trace, but paths have changed along the way, so we don't know where to correct it.

Hello,

Please open a ticket with Support. It's the best way to troubleshoot this. Also, it could be something not related to the version, etc.

We need to check logs, etc.

Thanks.

Regards,

Luciano Testa

However, the tip from two years ago turned out to be helpful. We solved the problem.

Hi Pawel,

I see. The path has not changed. 

In any case, I have to research this internally because applying those changes after 6.4.x should not be necessary.

Thanks for the feedback and for creating this thread.

Regards,

Luciano Testa

We have the same issue, which tip exact had resolved the problem? (Interessting it works for some minutes after reboot of the node, then same error)

However, it turned out that it does not fully work, and reading your description, it behaves in our case the same as in your description: sometimes it works, and other times a message about the lack of a chain appears. It started working when we increased the buffer from 8k to 16k - then the link to the request was longer and OWA was unable to handle it. Later, my friend reversed it and it also worked, but randomly.

Hello Pawel and Claus,

Just in case I went to Development and opened an internal ticket with them. They are researching this at the moment.

I expect to have an update later today.

Thanks.

Regards,

Luciano Testa

 Any news?

I observed following: (maybe that helps)

Login to the enrollment portal fails often with no chain found.

It works always if I use "repo\user" instead of only "user" (we use 3 repos, but username is unique", till 6.4.1 we don't have to specify the repo)

It works always with the old enrollment portal.

The "WebAuth feature is not running" error. Webauth (Groupwise OAuth) is only working after reboot (on the rebooted node only) for a short time.

Regards

Claus