Advanced Authentication (NetIQ) Discussions

This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

6.3.4 upgrade fails to authenticate to Filr

JvdMeij over 3 years ago

I have upgrade the Advanced Authentication from 6.3.3 to 6.3.4 security updates. Before I was able to login with the Filr Desktop Client and the web client. Now it hangs after the approval on my mobile and I am not able to login.

In the web client I see a message 'WebAuth feature is not running'.

In the Filr desktop client I get this error, but it was already there for a long time while it was working anyway:

[WARNING] Unhandled HTTP error: 302 (aa.<<domain>>/.../grant (aca.onprem.apiserver.restapi).

Anyone?

Top Replies

George Teys over 3 years ago in reply to jrmhscht +1

Yes, in 6.3.4 it happens for any OAuth 2.0 integration. In 6.3.4.1 this will be disabled by default and can be configured per event if needed.

0 JvdMeij over 3 years ago in reply to George Teys

Here you are.

aucore-logs_2021-04-12_2021-04-13.zip
Cancel
Vote Up 0 Vote Down

Cancel
0 George Teys over 3 years ago in reply to JvdMeij

The zip seems to be corrupted. It's only 230 bytes.
Cancel
Vote Up 0 Vote Down

Cancel
0 JvdMeij over 3 years ago in reply to George Teys

zuuut..

aucore-logs_2021-04-12_2021-04-13.zip
Cancel
Vote Up 0 Vote Down

Cancel
0 George Teys over 3 years ago in reply to JvdMeij

Based on the errors I see, I recommend creating a new OAuth 2.0 event and apply the new Event name, Client ID, and Client Secret on the Filr side.

If the issue still not solved after that and you see the same error, did you experience it in the previous version you had and which version you had before? 6.3.3?
Cancel
Vote Up 0 Vote Down

Cancel
0 jrmhscht over 3 years ago in reply to George Teys

I just ran into this same issue with Access manager (4.5.3.3). I tried creating a new event but that didn't help. I increased the nginx header size as suggested and then ran into the header size issue in access manager and had to increase that as well. Once the headers were increased on both systems it worked.
Is this suggested nginx change persistent in the container?
I had this issue in my production environment even though dev and test worked fine.
Is this a know issue in 6.3.4?

Thanks,
Jeremiah
Cancel
Vote Up 0 Vote Down

Cancel
0 George Teys over 3 years ago in reply to jrmhscht

Jeremiah, we are currently working on 6.3.4 Patch 1 that will have some new settings per Event to limit the number of returning groups. We hope to release it next week.
Cancel
Vote Up 0 Vote Down

Cancel
0 JvdMeij over 3 years ago in reply to George Teys

Hello George and others,
The thing with the groups is one thing. Hopefully another defect, known as defect 327040 will be solved with this patch.
Cancel
Vote Up 0 Vote Down

Cancel
0 George Teys over 3 years ago in reply to JvdMeij

On Thursday I had a conversation with development, they state it should be fixed as well.
Cancel
Vote Up 0 Vote Down

Cancel
0 jrmhscht over 3 years ago in reply to George Teys

Thanks for the update. Does the access manager integration with advanced auth pass groups?
Cancel
Vote Up 0 Vote Down

Cancel
0 George Teys over 3 years ago in reply to jrmhscht

Yes, in 6.3.4 it happens for any OAuth 2.0 integration. In 6.3.4.1 this will be disabled by default and can be configured per event if needed.
Cancel
Vote Up +1 Vote Down

Cancel

Menu

Advanced Authentication (NetIQ) Discussions

${resource:CF_GenericContent}test

6.3.4 upgrade fails to authenticate to Filr

Top Replies

Resources