Skip to main content

[archive] USERNAME Environment variable for AcuConnect 7.x

  • April 10, 2007
  • 1 reply
  • 0 views
D

[Migrated content. Thread originally posted on 20 March 2007]

Hi,

It seems in AcuConnect 5.x we could set an Environment variable of USERNAME to set the passed username to the server.

It seems in AcuConnect 7.x this isn't an option.

From the AcuConnect 5.1 doco:

4.2.5 Setting up the User Name

For Windows clients, the runtime uses the user name value that is set by the environment variable USERNAME. If USERNAME is not set, then the runtime uses the value that is set by the environment variable USER. (The values assigned to these variables are case-sensitive. Be sure that the case used in the "AcuAccess" file matches the case of the value set in the variable.) If neither of these environment variables is set, then the runtime uses the name "USER".

Under UNIX, the runtime uses the user name that the user logged in with.


I've read through the 7.2 doco and there doesn't appear to be anything mentioned about doing this.

Our software still sets USERNAME (actually it sets USERNAME, USER and DEFAULT_USER on the client just to make sure) but it always attempts to use the current Windows username to connect with AcuConnect.

I know there is an option on the server config file to use a "DEFAULT_USER" but that then sets all connections to the one user which makes it difficult to administer.

Any help appreciated.

Thanks,

Ray Smith


EDIT: (21/3/07) I have also sent this off to Acu Support. Will update this thread on any feedback from them.

    1 reply

    D

    [Migrated content. Thread originally posted on 20 March 2007]

    Hi,

    It seems in AcuConnect 5.x we could set an Environment variable of USERNAME to set the passed username to the server.

    It seems in AcuConnect 7.x this isn't an option.

    From the AcuConnect 5.1 doco:

    4.2.5 Setting up the User Name

    For Windows clients, the runtime uses the user name value that is set by the environment variable USERNAME. If USERNAME is not set, then the runtime uses the value that is set by the environment variable USER. (The values assigned to these variables are case-sensitive. Be sure that the case used in the "AcuAccess" file matches the case of the value set in the variable.) If neither of these environment variables is set, then the runtime uses the name "USER".

    Under UNIX, the runtime uses the user name that the user logged in with.


    I've read through the 7.2 doco and there doesn't appear to be anything mentioned about doing this.

    Our software still sets USERNAME (actually it sets USERNAME, USER and DEFAULT_USER on the client just to make sure) but it always attempts to use the current Windows username to connect with AcuConnect.

    I know there is an option on the server config file to use a "DEFAULT_USER" but that then sets all connections to the one user which makes it difficult to administer.

    Any help appreciated.

    Thanks,

    Ray Smith


    EDIT: (21/3/07) I have also sent this off to Acu Support. Will update this thread on any feedback from them.
    An update for anyone searching for an answer:

    I was contacted by Acu on the 28/3/07 and told:

    "there indeed might be some changes to the way server/client identities are determined".

    I emailed back some more info, but haven't heard anything since, so I assume unless you want to use the "DEFAULT_USER" option in the server config file (meaning all processes are owned by the one user), all Windows login user names must match the server login names (in this case Unix).

    This isn't a problem for new sites, but is a bit of a pain when upgrading existing sites where the login names don't match.

    Regards,

    Ray Smith

    Recent badge winners

    Explore all badges
    Terms & ConditionsAccessibility statement