Skip to content

feat: Support client authentication for UMA APIs - #101

Merged
jvherweg merged 1 commit into
mainfrom
feat/credential-validator
Sep 1, 2026
Merged

jvherweg merged 1 commit into
mainfrom
feat/credential-validator

Conversation

@jvherweg

Copy link
Copy Markdown
Contributor

This is so a client like LOAMA can access the resources API to know what all the resources are that a user owns.

@termontwouter

Copy link
Copy Markdown
Collaborator

Is there a specific reason LOAMA cannot use the user's token? Or is this meant for long-term offline access?

@jvherweg

Copy link
Copy Markdown
Contributor Author

I didn't actually even consider the idea of just also giving a PAT to the client :D . A PAT is specifically made for a single client though as it encodes that information, so a new PAT would have to be requested from the UMA server for the client. But would be possible. I did it like this because LOAMA already is using the standard authentication for everything else, but perhaps just using the PAT system that is already there would make more sense.

@jvherweg

jvherweg commented Sep 1, 2026

Copy link
Copy Markdown
Contributor Author

Merging to have this working. Created #103 to keep track of this.

@jvherweg
jvherweg merged commit 2e2d9f8 into main Sep 1, 2026
6 checks passed
@jvherweg
jvherweg deleted the feat/credential-validator branch September 1, 2026 07:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants