Linux connector SetPrompt validation IIQ 8.4

[robbe_deneef]

Which IIQ version are you inquiring about?

8.4p3

Share all details about your problem, including any error messages you may have received.

After upgrading from 8.3 to 8.4 we are seeing this difference in behaviour in an application using the “Linux - Direct“ connector.

All connections fail with this error:

[ InvalidConfigurationException ] [ Possible suggestions ] Make sure the application configuration attribute ‘SetPrompt’ is set with valid values. current value: unset PROMPT_COMMAND; PS1=‘SAILPOINT>’ [ Error details ] Invalid Shell Prompt

When logging in to the linux server interactively it accepts that command just as gracefully as before. It seems an extra validation was added on the connector level to check what a valid shell prompt should look like.

We were using the SetPrompt value to execute 2 commands on SSH login. Not only setting the prompt, but also clearing that $PROMPT_COMMAND variable.

This was needed as by default on our linux machine PROMPT_COMMAND will contain some “printf” stuff, giving feedback to the prompt on each command.
The IIQ connector doesn’t know what to do with that info, so if we don’t clear it every command will fail.

I understand we were maybe using this as a ‘trick’, and the extra validation is the desired behaviour.

But I was wondering if there is another way around this? Is there another way to tell the connector to run a specific command after each SSH login apart from the “SetPrompt“ setting?

(I have a workaround by modifying ~/.bash_user_profile on the linux server, clearing the variable on each login that way. But ideally I would like it to come from IIQ connector itself instead of managing those settings in the home dir of the connection user on each server)

[RAKRHEEM (Rakesh Bhati)]

@robbe_deneef

After upgrading from 8.3 to 8.4 we are seeing this difference in behaviour in an application using the “Linux - Direct“ connector.

All connections fail with this error:

[ InvalidConfigurationException ] [ Possible suggestions ] Make sure the application configuration attribute ‘SetPrompt’ is set with valid values. current value: unset PROMPT_COMMAND; PS1=‘SAILPOINT>’ [ Error details ] Invalid Shell Prompt

When logging in to the linux server interactively it accepts that command just as gracefully as before. It seems an extra validation was added on the connector level to check what a valid shell prompt should look like.

We were using the SetPrompt value to execute 2 commands on SSH login. Not only setting the prompt, but also clearing that $PROMPT_COMMAND variable.

This was needed as by default on our linux machine PROMPT_COMMAND will contain some “printf” stuff, giving feedback to the prompt on each command.
The IIQ connector doesn’t know what to do with that info, so if we don’t clear it every command will fail.

I understand we were maybe using this as a ‘trick’, and the extra validation is the desired behaviour.

But I was wondering if there is another way around this? Is there another way to tell the connector to run a specific command after each SSH login apart from the “SetPrompt“ setting?

(I have a workaround by modifying ~/.bash_user_profile on the linux server, clearing the variable on each login that way. But ideally I would like it to come from IIQ connector itself instead of managing those settings in the home dir of the connection user on each server)

This is a known issue after upgrading to IIQ 8.4—the Linux Direct connector now validates the SetPrompt value more strictly and rejects commands that don’t strictly set a prompt. Unfortunately, there’s currently no built-in connector setting to execute additional SSH commands on login outside of SetPrompt.

Your workaround (modifying ~/.bash_profile or ~/.bashrc on the Linux server to unset PROMPT_COMMAND) is the recommended approach. Alternatively, you could explore using a custom shell wrapper or adjusting the service account’s shell initialization files centrally if managing multiple servers.