Repository navigation
Conversation
|
Thanks for building on the scheme-level A few concerns on
On "Login and audience still need client configuration": the |
|
Great input, thanks! Agree on splitting this PR. STS is definitely the more established flow and seems closer to acceptance, and we can discuss direct JWT separately. Also agree on renaming the signing fields and requiring public values. We use the public tenant ID for both. Tokens and temporary credentials are obtained at runtime and stay out of STAC metadata. On scope, we need to explain where the coupling sits:
In our example storage permissions come from the assumed role or the gateway’s role checks. Our direct flow therefore needs no required storage scopes and can use an empty scope. But yes, other gateways may authorize through scopes and when required storage scopes are declared, they should be present in the access token and enforced by the gateway. So agree as well that provider-level scopes must work for all alternatives in auth:refs (otherwise, separate definitions are needed). Thanks for pointing to #50. If I understand correctly, for STS the ID token’s audience must include that client ID, which STS must accept. For direct JWT access, the gateway audience can differ from the login client ID. For next steps, I suggest:
|
|
Sounds good, the plan works for me. And yes, you read #50 correctly: for STS the ID token's One suggestion on the order: the STS PR doesn't need to wait for #50. You could open it now and add For the direct JWT PR, since your gateway authorizes on audience and client roles rather than scopes, it may be worth making Before going further, it would be good to hear @m-mohr's opinion on the overall direction: the split into two PRs, the |
|
As with #44, going through OpenAPI first would make sense. Do they have existing plans to align to? Haven't looked into the proposal myself yet. |
Addresses #47.
STAC login and S3 access are separate. GDAL/rasterio and fsspec/s3fs still
need S3 credentials. Today, that usually means extra setup for each provider.
Adds optional
credentialProviderto the existings3scheme: describes howa helper gets credentials for S3 SigV4 requests.
Changes
Three examples:
No credentials, signing, or Asset
auth:refs.AssumeRoleWithWebIdentity→ temporary S3 credentials.stsUrlandroleArnin metadata;RoleSessionNamegenerated by the client.Use the returned
AccessKeyId,SecretAccessKey, andSessionToken;renew before
Expiration.with the requested
scope. Tenant signing values; JWT inSessionToken.Gateway checks the JWT and access policy. No STS call; login and token
renewal still needed.
Both signed examples use
type: "s3". Provider type:assumeRoleWithWebIdentityorjwtSessionToken.Input scheme linked through scheme-level
auth:refs. Token kind fixed by theprofile; optional
subjectTokenTypeto state it explicitly.Also added the
Storage extension
to the examples:
object_storagefor endpoint, bucket, and region.Hope this use is fine.