
Security News
CVE Volume Surges Past 48,000 in 2025 as WordPress Plugin Ecosystem Drives Growth
CVE disclosures hit a record 48,185 in 2025, driven largely by vulnerabilities in third-party WordPress plugins.
@adobe/aio-cli-plugin-auth
Advanced tools
The IMS plugin to aio supports managing tokens for IMS such as login, logout, and retrieving and using tokens.
The Auth plugin to the Adobe I/O CLI supports managing tokens for Adobe Identity Management Services (IMS) such as login, logout, and retrieving and using tokens.
| Module | Version | Downloads | Build Status | Coverage | Issues | Pull Requests |
|---|---|---|---|---|---|---|
| @adobe/aio-lib-ims | ||||||
| @adobe/aio-lib-ims-jwt | ||||||
| @adobe/aio-lib-ims-oauth |
This plugin provides Adobe IMS support for authentication.
This plugin supports:
The collection of Adobe IMS supporting plugins:
This Adobe IO CLI Auth Plugin offers three commands:
login to create and return Adobe IMS access tokens. Since tokens are cached in the Adobe IO CLI configuration, an actual token is only created if the currently cached token has already expired (or is about to expire within 10 minutes).logout invalidate cached tokens and remove them from the cache. Besides the access token, this can also be used to invalidate any refresh token that may be cached.ctx to manage configuration contexts.$ aio plugins:install -g @adobe/aio-cli-plugin-auth
$ # OR
$ aio discover -i
$ aio auth --help
aio authAdobe IMS commands to login and logout.
USAGE
$ aio auth
DESCRIPTION
Adobe IMS commands to login and logout.
The main commands are `auth login` to get or create an access token and
`auth logout` to invalidate an access token and thus log out from Adobe IMS.
Logging in and out is based on configuration of which there may be
multiple. Each set of configuration properties, called an Adobe IMS context,
can be individually addressed by a label.
Configuration for the Adobe IMS commands is stored in the "ims"
configuration property. The special property "ims.config.current" contains the
label of the current configuration which can be set using the
"aio auth ctx -s <label>" command.
Each set of properties in a labeled Adobe IMS context configurations has
configuration properties depending on the kind of access that is
supported. The below example shows the configuration for OAuth2
based (graphical SUSI) login.
The "env" property is optional and designates the Adobe IMS environment
used for authentication. Possible values are "stage" and "prod".
If the property is missing or any other value, it defaults to "prod".
All commands allow their normal output to be formatted in either
HJSON (default), JSON, or YAML.
EXAMPLES
{
ims: {
contexts: {
postman: {
env: "stage",
callback_url: "https://callback.example.com",
client_id: "example.com-client-id",
client_secret: "XXXXXXXX",
scope: "openid AdobeID additional_info.projectedProductContext read_organizations",
state: ""
}
},
config: {
current: "postman"
}
}
}
See code: src/commands/auth/index.js
aio auth ctxManage Adobe IMS contexts.
USAGE
$ aio auth ctx [--debug <value>] [-v] [-l | -g] [-c <value>] [--list | --value | -s <value> | ]
FLAGS
-c, --ctx=<value> Name of the Adobe IMS context to use. Default is the current Adobe IMS context
-g, --global global config
-l, --local local config
-s, --set=<value> Sets the name of the current local Adobe IMS context
-v, --verbose Verbose output
--debug=<value> Debug level output
--list Names of the Adobe IMS contexts as an array
--value Prints named or current Adobe IMS context data
DESCRIPTION
Manage Adobe IMS contexts.
The following options exist for this command:
* List the names of the configured Adobe IMS contexts
* Print the name of the current Adobe IMS context
* Set the name of the current Adobe IMS context
* Print the configuration of the current or a named Adobe IMS context
Currently it is not possible to update the Adobe Adobe IMS context configuration
using this command. Use the "aio config" commands for this.
e.g. aio config:set ims.contexts.your_context.your_context_key "your_context_value"
Please note, that the following IMS context label names is reserved: `cli`
and should not be used as an IMS context name.
Also note that the current context can only be set locally.
ALIASES
$ aio ctx
$ aio context
See code: src/commands/auth/ctx.js
aio auth loginLog in with a certain Adobe IMS context and returns the access token.
USAGE
$ aio auth login [--debug <value>] [-v] [-l | -g] [-c <value>] [-f] [-d] [-b] [-o]
FLAGS
-b, --bare print access token only
-c, --ctx=<value> Name of the Adobe IMS context to use. Default is the current Adobe IMS context
-d, --decode Decode and display access token data
-f, --force Force logging in. This causes a forced logout on the context first and makes sure to not use any
cached data when calling the plugin.
-g, --global global config
-l, --local local config
-o, --[no-]open Open the default browser to complete the login
-v, --verbose Verbose output
--debug=<value> Debug level output
DESCRIPTION
Log in with a certain Adobe IMS context and returns the access token.
If the Adobe IMS context already has a valid access token set (valid meaning
at least 10 minutes before expiry), that token is returned.
Otherwise, if the Adobe IMS context has a valid refresh token set (valid
meaning at least 10 minutes before expiry) that refresh token is
exchanged for an access token before returning the access token.
Lastly, if the Adobe IMS context properties are supported by one of the
Adobe IMS login plugins, that login plugin is called to guide through
the IMS login process.
The currently supported Adobe IMS login plugins are:
* aio-lib-ims-jwt for JWT token based login supporting
Adobe I/O Console service integrations.
* aio-lib-ims-oauth for browser based OAuth2 login. This
plugin will launch the default browser to guide the user through the
login process. The plugin itself will *never* see the user's
password but only receive the authorization token after the
user has authenticated with Adobe IMS.
ALIASES
$ aio login
See code: src/commands/auth/login.js
aio auth logoutLog out the current or a named Adobe IMS context.
USAGE
$ aio auth logout [--debug <value>] [-v] [-l | -g] [-c <value>] [-f]
FLAGS
-c, --ctx=<value> Name of the Adobe IMS context to use. Default is the current Adobe IMS context
-f, --[no-]force Invalidate the refresh token as well as all access tokens.
Otherwise only the access token is invalidated. For Adobe IMS
contexts not supporting refresh tokens, this flag has no
effect.
-g, --global global config
-l, --local local config
-v, --verbose Verbose output
--debug=<value> Debug level output
DESCRIPTION
Log out the current or a named Adobe IMS context.
This command can be called multiple times on the same Adobe IMS context with
out causing any errors. The assumption is that after calling this command
without an error, the Adobe IMS context's access and refresh tokens have been
invalidated and removed from persistent storage. Repeatedly calling this
command will just do nothing.
ALIASES
$ aio logout
See code: src/commands/auth/logout.js
Contributions are welcomed! Read the Contributing Guide for more information.
This project is licensed under the Apache V2 License. See LICENSE for more information.
FAQs
The IMS plugin to aio supports managing tokens for IMS such as login, logout, and retrieving and using tokens.
The npm package @adobe/aio-cli-plugin-auth receives a total of 3,113 weekly downloads. As such, @adobe/aio-cli-plugin-auth popularity was classified as popular.
We found that @adobe/aio-cli-plugin-auth demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 22 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
CVE disclosures hit a record 48,185 in 2025, driven largely by vulnerabilities in third-party WordPress plugins.

Security News
Socket CEO Feross Aboukhadijeh joins Insecure Agents to discuss CVE remediation and why supply chain attacks require a different security approach.

Security News
Tailwind Labs laid off 75% of its engineering team after revenue dropped 80%, as LLMs redirect traffic away from documentation where developers discover paid products.