Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Review usage of "one domain" and "another domain" #122

Open
PieterKas opened this issue Dec 16, 2024 · 2 comments
Open

Review usage of "one domain" and "another domain" #122

PieterKas opened this issue Dec 16, 2024 · 2 comments

Comments

@PieterKas
Copy link
Contributor

Editorial review on the use of language of "one domain" and "another domain" and replacing it with "Domain A" and "Domain B" for clarity and consistency.
@kburgin3
Copy link
Contributor

kburgin3 commented Jan 6, 2025

Editorial review on the use of language of "one domain" and "another domain" and replacing it with "Domain A" and "Domain B" for clarity and consistency.

I'm in favor of this

@PieterKas
Copy link
Contributor Author

I will prepare a PR :)

PieterKas added a commit that referenced this issue Jan 9, 2025
@PieterKas
Clarify AS-as-Client (#119)
6be8a31 
* Clarify AS-as-Client 

Added text and diagrams to clarify Authorization-server-as-aclient flows.

* Resource server replace by client

Aligning on client terminology to align with main specification.

* removing trailing white spaces

* removes "one domain" and "another domain"

Change made as suggested by @kburgin3

Related to issue #122
PieterKas added a commit that referenced this issue Jan 9, 2025
@PieterKas
Clarify resource server as client (#118)
9f85675 
* Clarify resource server as client

Modified diagram and added additional text to describe the resource server acting as a client.

* Updated based on feedback from Kelley

Related to issue #122
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kburgin3 @PieterKas