FFFF Update with core authn team by abstractj · Pull Request #47780 · keycloak/keycloak · GitHub
[go: up one dir, main page]

Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions .github/teams.yml
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,16 @@ team/core-iam:
- area/user-profile
- area/workflows

team/core-authn:
- area/account/ui
- area/admin/ui
- area/authentication
- area/core
- area/identity-brokering
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one is right now for core-iam. I suppose that only the authentication stuff related to identity brokering is for us, not the identity provider implementation. In such case, I would say that this one should remain in core-iam, only the stuff that is related to authentication via identity providers is for us. They can assign to us issues that are more area/authentication than area/identity-brokering.

- area/saml
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it mean, the SAML is shared for the protocols and authn?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SAML is strictly speaking a protocol, but, as I usually managed the issues related to SAML, don't know who is going to be the responsible. @mposolda WDYT? Do we share SAML for the moment?

- area/test-framework
- area/token-exchange/subject-impersonation
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it intentional to have the area/token-exchange for core-protocols, and area/token-exchange/subject-impersonation for core-authn?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would assign TE as a whole to one or both teams. Assigning just a minor part makes no sense. If we should start doing the delegation part we can share the area/token-exchange for the moment.


team/core-shared:
- area/account/api
- area/admin/api
Expand Down
0