Oauth browser path not found 404

Server Administration - Administration-du-Serveur
1

we had a working oauth authentification flow between one of our app and dhis2
but it seem that after the redirection to

https://dhis2.domain/uaa/oauth/authorize/?client_id=orbf2&response_type=code

we get the tomcat error

# HTTP Status 404 – Not Found

---

**Type** Status Report

**Message** No static resource uaa/oauth/authorize.

**Description** The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.

was there any changes in the oauth flow in 2.4x ? (here 2.42)
the documentation still mention that url : Introduction - DHIS2 Documentation

thank you

1 Like
2

Hi @Stephan_Mestach

Thank you for your post. I guess the docs need updating because it’s mentioned in the release notes starting from version 2.42 “remove OAuth2 from settings app v42”, and it’s mentioned in the ‘deprecated features’ notes that “The old and deprecated OAuth support will be removed” (see table ‘Removed features’ row 4).

If you face any issue to start using the new supported OAuth 2.0 then please feel free to reply here.

Thanks!

1 Like
3

Can you point me to the OAuth 2.0 ? I still end up with the wrong path/flow
(I’m using the web flow)

1 Like
4

Hi Stéphan,

I’m sorry to inform that the documentation for 2.42 is very outdated.
We did a big change to the OAuth2 backend in 2.42 and it’s now served by the Spring Authorization server project.
The quickest way to get up to date, is probably to have a look at this test:

This test does a full e2e authorization code flow test.
If you have any questions you can contact me directly also.
It’s on the agenda to get the documentation updated soon.

2 Likes
5

Hello @netroms and @Gassim I am a little confused by the links:

says: remove OAuth2

says: The old and deprecated OAuth support will be removed
and just up above: Oauth browser path not found 404 - #2 by Gassim
says: “the new supported OAuth 2.0”

So I wanted to ask, is DHIS 2 supporting OAuth 2.0 going forward or not?
And how does this affect OIDC with Azure/Google/Okta?

1 Like