Difference: APPXLoginManagerForUnixLinux (67 vs. 68)

Revision 682018-01-19 - JeanNeron

Line: 1 to 1

META TOPICPARENT	name="APPX500Features"

APPX Login Manager For Unix/Linux

This page describes how to install the APPX Login Manager command and how to use it to install, configure, and manage APPX Login Services on Unix/Linux systems.

Changed:

<
<

>
>

The APPX Login Manager command is used to configure and manage APPX Login Services.

Line: 196 to 196

-initScript={lsb, <nop>RedHat}

Used with -install option to specify the type of operating system that the service script is to be created for. If this option is not specified, appxLoginMgr will determine which type of service script to install.

Added:

>
>

serverEnableHTTPdebug={true, false}

Normally you can point a browser at the login port & it will display a configuration page. This might be considered a security risk, setting this to a value of 'false' will cause the listener to immediately hang up and recycle to a listening state on an HTTP request without displaying the configuration information.

Options - Session Identity/Permissions

-ImpersonateUID={true, false}

Line: 659 to 664

Exit - This will exit the session manager without logging in to APPX.

Issues:

Changed:

<
<

The stop option of the Red Hat service command has a problem. It does seem to remove the running process; however, it produces errors. Further, it fails to remove the PID from the (/var/run/appx-8060.pid)
```
/etc/init.d/appx-8060: line 39: success: command not found
/etc/init.d/appx-8060: line 39: failure: command not found
/etc/init.d/appx-8060: line 43: failure: command not found
```

>
>

The stop option of the Red Hat service command has a problem. It does seem to remove the running process; however, it produces errors. Further, it fails to remove the PID from the (/var/run/appx-8060.pid)
```
/etc/init.d/appx-8060: line 39: success: command not found
/etc/init.d/appx-8060: line 39: failure: command not found
/etc/init.d/appx-8060: line 43: failure: command not found
```

The setuid warning message is displayed every time a configuration is loaded or saved. This results in the message being displayed up to three times depending on the command being executed. Perhaps it should only be displayed when a configuration is saved.
The setuid warning indicates that it is triggered by the OSUser AuthenticationMethod. AuthenticationMethod is not influenced by the setuid bit being turned on. However, ImpersonateUser is impacted.

Comments:

Line: 668 to 673

Changed:

<
<

<--/commentPlugin-->

>
>

<--/commentPlugin-->

View topic | History: r68 < r67 < r66 < r65 | More topic actions...