access-token-provider alternatives and similar packages
Based on the "Data" category.
Alternatively, view access-token-provider alternatives based on common mentions on social networks and blogs.
-
-
-
-
-
-
compendium-client
DISCONTINUED. Mu (μ) is a purely functional framework for building micro services. -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
text-icu
This package provides the Haskell Data.Text.ICU library, for performing complex manipulation of Unicode text. -
-
streaming
An optimized general monad transformer for streaming applications, with a simple prelude of functions -
-
CodeRabbit: AI Code Reviews for Developers
Do you think we are missing an alternative of access-token-provider or a related project?
README
Access Token Provider 
This package provides a convenient retrieval mechanism for access tokens. Multiple provider backends, including OAuth2 Resource Owner Password Credentials Grant, file-based token access (e.g. for Kubernetes) and fetching tokens from the environment (e.g. for local testing) are supported; custom provider backends can easily be added.
Examples
import qualified Security.AccessTokenProvider as ATP
retrieveSomeToken :: IO ()
retrieveSomeToken = do
tokenProvider <- ATP.new (AccessTokenName "token-name")
token <- ATP.retrieveAccessToken tokenProvider
print token
Configuration
Configuration is done by setting certain environment variables, depending on the provider.
OAuth2 based token retrieval
The OAuth2 (Resource Owner Password Credentials Grant) provider
expects the ATP_CONF_ROPCG environment variable to contain a JSON
object as follows:
{
"credentials_directory": "/optional/credentials/directory",
"auth_endpoint": "<OAuth2 authentication endpoint>",
"tokens": {"token-name": {"scopes": ["first-scope", "second-scope"]}}
}
The credentials_directory setting defaults to the content of the
environment variable CREDENTIALS_DIR. It is expected to contain the
files user.json and client.json, containing the user and client
credentials respectively.
File based token retrieval (e.g. for Kubernetes)
The file based provider expects the ATP_CONF_FILE environment
variable to contain a JSON object as follows:
{
"tokens": {"token-name": "/some/file/name"}
}
As a short cut, you can simply save a token path directly in the
environment variable TOKEN_FILE.
Environment based token retrieval (e.g. for testing)
The file based provider expects the ATP_CONF_FIXED environment
variable to contain a JSON object as follows:
{
"tokens": {"token-name": "some-fixed-token"}
}