FederatedStore-FederatedAccess: Inappropriate usage of GraphAuths arguments
See original GitHub issueFederatedStore-FederatedAccess: Inappropriate usage of GraphAuths Arguments
During a AddGraph Operation a User can set graphAuths
and readAccessPredicates
.
The following code appears to junk the graphAuths
if readAccessPredicate
was set.
this.readAccessPredicate = new String(JSONSerialiser.serialise(readAccessPredicate != null ? readAccessPredicate : new FederatedGraphReadAccessPredicate(addingUserId, graphAuths, isPublic)));
This will be confusing usage for setting authorisations. It is likely that the graphAuths
should be merged into the readAccessPredicate
.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Securing a federated graph - Apollo GraphQL Docs
First, we'll explore the attack surface of GraphQL APIs and effective mitigation strategies. We'll also discuss a common approach for handling authentication ......
Read more >Overview of federated identity credentials in Azure Active ...
Federated identity credentials allow you to access Azure and Microsoft Graph resources without having to manage secrets.
Read more >Using a federated identity to manage Amazon Redshift access ...
Using identity federation in AWS with credentials provided from GetDatabaseCredentials can simplify authorization and access to local data and to external data.
Read more >View of Economic tussles in federated identity management
Such systems allow a user to authenticate once — single sign–on (SSO) — and then use that identity to access information across multiple...
Read more >OpenID Connect vs OAuth vs SAML 2 - Security Journey
There are three major protocols used by companies for federated identity: ... Authentication and Authorization are two terms and different ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Made these changes together with those for #2320. I’ve applied @GCHQDev404’s suggestion to prevent users from mixing “old” auth configuration with the “new” AccessPredicate mechanism to Federated Access, Named Views and Named Operations which all behave similarly.
Yeah that’s fair. I agree throwing an exception if both are set is nicer.