#Auth happens on page refresh, everytime

1 messages · Page 1 of 1 (latest)

mortal yoke
#

I am getting a new behavior that after a good auth session backstage with a hard refresh goes back through auth again as if I had logged out.

The console error shows a 401 to this route:
/api/auth/microsoft/refresh?optional&env=development

The environment is not development it is our staging environment and I am curious if this behavior is due to our app-copnfig.yaml file containing:

auth:

see https://backstage.io/docs/auth/ to learn about auth providers

environment: development
providers:
microsoft:
development:

We have one app-config.yaml that we transform the contents via env vars at runtime. I wasn't sure if that mattered at all since the what should matter is:
development:
clientId: ${AUTH_MICROSOFT_CLIENT_ID}
clientSecret: ${AUTH_MICROSOFT_CLIENT_SECRET}
tenantId: ${AUTH_MICROSOFT_TENANT_ID}

Authentication in Backstage | Backstage Software Catalog and Develo...

Introduction to authentication in Backstage

mortal yoke
#

@abstract matrix any reaction to this?

abstract matrix
#

I don't really understand what you are doing and why. Some steps to reproduce could help me understand better, please.

mortal yoke
#

@abstract matrix steps to reproduce:
open backstage app in chrome (our internal url), Azure auth happens.
Browse to components (catalog)
Refresh the browser - Auth provider popup appears and goes through auth process again

In browser console there is a persistent 401 error, even though the end user can access everything in backstage

abstract matrix
#

Thanks, will try this. In the mean time what version of Backstage are you on?

mortal yoke
#

1.17.0

abstract matrix
#

Ok, just tried this in dev, stage, and prod where we are on 1.18.0-next.2 and no issues, nothing in the console, everything works fine

#

Sorry, I know that's not super helpful but at least you know it's working for others.

mortal yoke
#

@abstract matrix thanks for checking, I think it might be a caching issue

#

@abstract matrix I am also getting an odd error in our staging environment where the dry run is returning a 400, I have double checked our GitHub app settings and it all looks good.

{
"error": {
"name": "InputError",
"message": "Error: Unable to read url, HttpError: fetch failed"
},
"request": {
"method": "POST",
"url": "/locations?dryRun=true"
},
"response": {
"statusCode": 400
}
}

abstract matrix
#

No idea, not something I’ve used.

mortal yoke
#

@abstract matrix this error occurs when I click analyze on importing a component it looks like the request is missing the baseURL

abstract matrix
#

Ok, that's also not something we use so not going to be terribly helpful

quartz wigeon
mortal yoke
velvet finch
#

I'm experiencing the same issue with pingfed Auth. On refresh I'm returned to the login page with a 401 error in the network tab.

Was there any other solution?

cosmic sparrow
#

@velvet finch I think that you will need to enable the offline_access or offline scope to the auth provider.

#

Has some examples for Azure auth