-
Notifications
You must be signed in to change notification settings - Fork 654
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
[Docs] Update auth_setup.rst #5863
base: master
Are you sure you want to change the base?
Conversation
Fixed the following issues: 1. The steps for MS Entra ID have to be updated to reflect the current location of settings on the Azure UI 2. fixed indentation error in ``configmap.adminServer.security`` 3. Step 8 and beyond are folded inside the Note block when it should be out. 4. made the intro slightly easier to read. Signed-off-by: Pranshu <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5863 +/- ##
=======================================
Coverage 36.72% 36.72%
=======================================
Files 1304 1304
Lines 130072 130072
=======================================
Hits 47764 47764
Misses 78138 78138
Partials 4170 4170
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
As defined by IETF's `RFC #6749 <https://datatracker.ietf.org/doc/html/rfc6749>`__, the authorization server's role is to issue *access tokens to the client after successfully authenticating the resource owner and obtaining authorization*. In this context, the *resource owner* is the end user of Flyte; and the *client* is the tool or component that intends to interact with ``flyteadmin`` : ``flytepropeller``, ``flyteconsole`` or any of the CLI tools. | ||
As defined by IETF's `RFC #6749 <https://datatracker.ietf.org/doc/html/rfc6749>`__ , the authorization server’s job is to issue access tokens to clients after verifying the user (resource owner) and getting their consent. In this setup: | ||
|
||
1. The user of Flyte, is the *resource owner*. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried it without indentation but then the whole authorization server paragraph becomes italics for some reason. If you can suggest a fix for that please do.
Tracking issue
Closes #5552
Why are the changes needed?
The docs had a few issues as mentioned in the issue and the intro was slightly hard to read and understand.
What changes were proposed in this pull request?
configmap.adminServer.security
was corrected.Check all the applicable boxes
Docs link
Authenticating in Flyte page, changes mentioned above