Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
OAuth2.0 Integration for Web UI
See original GitHub issueBackground information:
Currently, we @ zalando have a “zally-web-ui appliance” project. It is mainly used to integrate OAuth2.0 by implementing OAuth flow on top of @zalando/zally-web-ui package. The result is deployed within the Zalando organization.
If I remember correctly, we initially decided to split up these projects to hide internal details about Zalando’s infrastructure. But there is probably a way to make it configurable 😉
User Story As a Zally maintainer I want to include OAuth2.0 integration In order to:
- enable OAuth2.0 for others
- simplify build and release process
- enable continuous delivery with CDP (Zalando’s continuous delivery platform)
- simplify the project setup
Acceptance criteria
@zalando/zally-web-uican still be published as NPM package- CDP builds
zally-web-ui-alphadocker image on every change of/web-ui - OAuth2.0 integration is disabled per default
- docker-compose script doesn’t break
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thanks for the heads-up! FWIW we do have the web-ui running internally but actively disable the “production” profile since we don’t feel the need to involve authz/n for Zally. I’ll keep an eye out for any further pull requests related to this issue just in case.
This issue is opened for a long time and we didn’t make any progress - the priorities have shifted. Closing…