Skip to content

Handling custom tokens #192

@simongottschlag

Description

@simongottschlag

Checklist

Describe the problem you'd like to have solved

We currently have to create a custom http message handler and then create a http client from it and then pass the http client. This is a bit weird in our case since we want to use the same http client (not true, same connection pool) for all services and this becomes a bit interacte.

Describe the ideal solution

It would be nice to be able to pass the default http client and then maybe a delegate (higher-order function) which extracts the token. Not sure exactly how this should look to be idiomatic, but in our case we are using Entra as the OP for OpenFGA and using the default Azure SDK for authentication and want to reuse it.

Alternatives and current workarounds

Create custom http message handler that’s passed to http client which is then passed to OpenFgaClient constructor.

References

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    Status

    Intake

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions