Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.
I am seeing an error attempting to run the ‘sail env create’ command on my RHEL 9 server. Additional details are shared below.
Please consider addressing the following when creating your topic:
What have you tried?
Trying to set an environment for the CLI, I receive the error “Error: The name is not activatable”
What errors did you face (share screenshots)?
“Error: The name is not activatable”
Share the details of your efforts (code / search query, workflow json etc.)?
I’ve tried multiple things. I set the environment variables for SAIL_BASE_URL, SAIL_CLIENT_ID, and SAIL_CLIENT_SECRET as directed in the instructions. This does seem to work when I run many of the ‘sail’ commands. What doesn’t seem to be working is when I try to create a new environment.
What is the result you are getting and what were you expecting?
I would expect the environment can be setup successfully so I can create multiple environments within the configuration.
I do see a warning also which may be related.
#> /usr/sail rule list
2026/04/20 09:42:19 WARN Secrets storage is not currently functional on this platform, PAT will only work with environment variables additional information=URL
2026/04/20 09:42:19 WARN Secrets storage is not currently functional on this platform, PAT will only work with environment variables additional information=URL
Has anyone encountered this error before and have any idea what can help with RHEL 9 configuration to make this configuration work? Thank you.
I think the conflict here may be that you are using environment variables, AND trying to use the sail env create command.
I’ve not personally used the environment variables because I work in multiple environments, and want to be able to use the sail env use command to switch between them all.
If you look at the documentation, it describes the use of sail env create, and then later also states “You can also store your configuration in environment variables. This can be useful when you are using the CLI in an automated environment like a continuous integration and continuous deployment (CI/CD) pipeline”. I take this to imply that you either create and manage your environment using the sail env commands, or by setting up environment variables. Try executing the sail env commands without having any environment variables set within your shell and see if that makes any difference.
I don’t see any specific packages listed for Linux in the documentation you shared. Only the RPM package the I had already installed. Perhaps you could elaborate on what those packages are in this thread? I may be missing something.
Some new developments. First, I deleted the .sailpoint folder containing the config.yaml. Doing that did not yield any different result. Also, considering its a permissions related issue on the server, I elevated my access on the server running ‘sudo sail env create’ and the error message changed. The following error displayed when I elevated to root.
Error: The name org.freedesktop.secrets was not provided by any .service files
OK, it looks like the errors are related specifically to the storage of the client id/secret. If I just create the environment without selecting an auth type and then supply the environment variables when I run the CLI, I don't get the errors and don't need to install any additional packages.
Unfortunately, this just isn’t working. I do bypass the Authentication Type setting and it returns a message like it was successful (Environment successfully created.). However, after I attempt to create both production and sandbox configurations, it tells me the envs do not exist.
[axz031@eiam01pa ~]$ /usr/sail env use jefferson-production
2026/04/21 11:09:11 WARN Environment does not exist
Use `sail env create jefferson-production` to create it.
[axz031@eiam01pa ~]$ /usr/sail env use jefferson-sandbox
2026/04/21 11:09:18 WARN Environment does not exist
Use `sail env create jefferson-sandbox` to create it.
[axz031@eiam01pa ~]$ sudo /usr/sail env use jefferson-sandbox
2026/04/21 11:09:21 WARN Environment does not exist
Use `sail env create jefferson-sandbox` to create it.
[axz031@eiam01pa ~]$ sudo /usr/sail env use jefferson-production
2026/04/21 11:09:30 WARN Environment does not exist
Use `sail env create jefferson-production` to create it.
I think you are right. I just noticed this message when I ran with the environment variables. This seems to imply the same as you mentioned. Thanks for all the information. At least I know where I stand.
Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.
