-
Notifications
You must be signed in to change notification settings - Fork 331
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
feat: saml upload #9750
feat: saml upload #9750
Conversation
Signed-off-by: Matt Krick <matt.krick@gmail.com>
@@ -61,7 +63,7 @@ const permissionMap: PermissionMap<Resolvers> = { | |||
SAMLIdP: rateLimit({perMinute: 120, perHour: 3600}) | |||
}, | |||
Organization: { | |||
saml: and(isViewerBillingLeaderSource, isOrgTierSource('enterprise')) | |||
saml: and(isViewerBillingLeader('source.id'), isOrgTier('source.id', 'enterprise')) |
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.
curious on your thoughts about this new pattern.
I want to reuse rules as much as I can. For example, this rule requires an orgId to determine if the viewer is on the org. That orgId
may exist in an arg, or in the source, and it could have any name. I think a dot notation path is the cleanest way to do this, but wonder what you think?
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 like it! Not having type safety is my main concern, but that's still probably safer that accidentally mixing isOrgTierSource
for isOrgTier
@@ -61,7 +63,7 @@ const permissionMap: PermissionMap<Resolvers> = { | |||
SAMLIdP: rateLimit({perMinute: 120, perHour: 3600}) | |||
}, | |||
Organization: { | |||
saml: and(isViewerBillingLeaderSource, isOrgTierSource('enterprise')) | |||
saml: and(isViewerBillingLeader('source.id'), isOrgTier('source.id', 'enterprise')) |
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 like it! Not having type safety is my main concern, but that's still probably safer that accidentally mixing isOrgTierSource
for isOrgTier
Description
fix #9254
Supports uploading an XML file, which can then be used for the metadata URL
Demo
https://www.loom.com/share/23e34f4943ca4650803c9faad05bc488?sid=9d52a92c-093b-4b88-8bc3-8f37c31db1ca