-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Plugin doesn't work with the new backend architecture #8
Comments
@javier-fiore
I have all the setup in local network so for me it's pretty safe. Backstage forced auth internally between plugins. I have no idea where do I need set those internal credentials, so I just allowed access without them. |
It works, but I am afraid to use this kind of configuration. At this time, ti works as workaround, but i think that there is a bug here. Thanks a lot! |
+1, requiring adopters to disable backend authentication shouldn't be an acceptable workaround for production systems. Looking through the code, it looks like this plugin uses the circleci-api package to make requests, overwriting the URL to use the backend proxy. I think it should be possible to use the Backstage IdentityApi to add the user's Backstage authentication information to the request so that the Backstage backend auth system doesn't return a 401, but would leave this up to the maintainers to decide the best path here. |
When we try to use this plugin whit the new backend architecture, we receive a 401 unauthorized when it try to access to circleCI api.
Maybe you must update this repo with the scaffolding created with create-app program to make it work with the new backstage.
The text was updated successfully, but these errors were encountered: