Authorization using pxctl
This document outlines how to interact with an auth-enabled Portworx cluster. The main way to do it is by using the
pxctl context commands. In addition, you can integrate with an OIDC provided token or generate self-signed tokens through
pxctl allows you to store contexts and associated clusters, privileges, and tokens local to your home directory. This way, you can easily switch between these configurations with a few commands.
pxctl contextis stored locally per node, you will need to create your context on the node you’re working on.
To find out the available commands, type:
/opt/pwx/bin/pxctl context --help
Portworx pxctl context commands for setting authentication and connection info Usage: pxctl context [flags] pxctl context [command] Available Commands: create create a context delete delete a context list list all contexts set set the current context unset unset the current context
You can easily create and delete contexts with the following commands:
Creating or updating a context:
pxctl context create <context> --token <token> --endpoint <endpoint>
Deleting a context:
pxctl context delete <context>
Listing your contexts:
Your contexts live in
~/.pxctl/contextconfig. You can easily view them with the
pxctl context list
contextconfig: current: user configurations: - context: user token: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJlbWFpbCI6ImpzdGV2ZW5zQHBvcnR3b3J4LmNvbSIsImV4cCI6MTU1MzcyNTMyMSwiZ3JvdXBzIjpbInB4LWVuZ2luZWVyaW5nIiwia3ViZXJuZXRlcy1jc2kiXSwiaWF0IjoxNTUzNjM4OTIxLCJpc3MiOiJwb3J0d29yeC5jb20iLCJuYW1lIjoiSmltIFN0ZXZlbnMiLCJyb2xlcyI6WyJzeXN0ZW0udXNlciJdLCJzdWIiOiJqc3RldmVuc0Bwb3J0d29yeC5jb20vanN0ZXZlbnMifQ.pZDbCIL7ldcImvIaNSjk18Ah3LqxX63MV378NiauRwk identity: subject: email@example.com/jstevens name: Jim Stevens email: firstname.lastname@example.org endpoint: http://localhost:9001
Now that you’ve created your contexts, you can easily switch between them with the commands below.
pxctl will automatically read your currently set context and use the associated token for all commands.
Alternatively, you can use the global
--context flag to run a single command with a given context.
Setting current context:
pxctl context set <context>
Unsetting current context:
pxctl context unset
Portworx supports two methods of authorization: OIDC and self-signed.
For generating a token through your OIDC provider, see your provider’s documentation on generating bearer tokens. The following are some of the supported OIDCs:
For self-signed, you can use your own JWT compliant application, or for
pxctl has a command for generating tokens.
Generating self-signed tokens:
pxctl allows you to generate self-signed tokens in a few different ways:
ECDSA, RSA, and Shared-Secret. In addition to these parameters, you must pass an
authconfig.yaml. See below for an example with configuration
pxctl auth token generate --auth-config=<authconfig.yaml> --issuer <issuer> \ --ecdsa-private-keyfile <ecdsa key file> OR \ --rsa-private-keyfile <rsa key file> OR \ --shared-secret <secret>
Sample configuration (authconfig.yaml):
name: Jim Stevens email: email@example.com sub: firstname.lastname@example.org/jstevens roles: ["system.user"] groups: ["*"]
Debugging token issues
Permission denied issues
You may have gotten an unexpected
"Permission denied" or other auth-related error. To take a look into your token permissions, you can always decode it with a JWT token decoding tool such as jwt.io
If you’re seeing the below error:
rpc error: code = Internal desc = stream terminated by RST_STREAM with error code: PROTOCOL_ERROR
Make sure that your token does not accidentally contain a newline character. This is due to gRPC/http2 not allowing newline characters.
- For information about enabling and managing Portworx authorization through Kubernetes, refer to the Authorization page.