An open discussion list for topics related to the geteduroam service

[Jørn Åne de Jong <jornane.dejong AT surf.nl>]

On 17/08/2022 14:54, Darren Boss (via geteduroam Mailing List) wrote:
> I redeployed the portal on Debian 11.4 (Bullseye) but now I'm getting a error 
> 400 on the call from the Android app to /api/eap-config/. I decided to log 
> the Authorization header to a custom log and was able to decode it using a 
> JWT decoder. Looks fine, sub claim is my email address (using email nameid 
> from Azure AD). Including the decoded JWT in case it's something obvious:
>
> {
>    "__t": "access_token",
>    "iat": "1660739494",
>    "sub": "Darren.Boss AT alliancecan.ca",
>    "realm": "alliancecan.ca",
>    "scope": "eap-metadata",
>    "code_challenge_method": "S256",
>    "code_challenge": "LQpjYE1ZjYAC6i9OwaU3OFYUBR9-rV-X0ohvYcXpLi4",
>    "client_id": "app.eduroam.geteduroam",
>    "redirect_uri": "app.eduroam.geteduroam:/",
>    "exp": "1676637094"
> }
>
> jwt.io is flagging the dates as invalid but they look right to me and the iat 
> matches the date of the apache log entry.

I think the dates are supposed to be ISO strings.  I'll fix that in a 
future release, but it's not really a problem since we don't need 
interoperability with other solutions.

Error 400 means typically something wrong with the OAuth request.  Can 
you find the answer body?  It should tell you what's wrong.

--
Jørn Åne de Jong
geteduroam