We have a multi-client environment. I am connecting remedy with LDAP of
our base company but none of the rest becuase they all have different ldap
servers. My problem is that we identify each client with their
login in remedy(for the most part) but some cases this is not
true. All of our base client accounts are pulled from HR and a
is attached to the login name. Problem is I cannot use the login from ldap
directly. I need to strip off the then identify the user or let
them type in there login name without the but map it to the
correct login name in the system.

I also need to be able to maintain the ability for the users to submit
tickets and modify these tickets without using a licenses. I have not used
the ldap interface much is there a good way to manipulate the interface so
that I can use the authentication of ldap and still maintain my format of
login and also maintain the submitter priviledges for modification
without a licenses (floating).

Darrel


UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org)

Check out the Remedy knowledge base article which
talks about the Authentication Login Name.

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Darrel Fossett
Sent: Tuesday, November 08, 2005 4:09 PM
To: arslist@ARSLIST.ORG
Subject: LDAP mapping

We have a multi-client environment. I am connecting remedy with LDAP of
our base company but none of the rest becuase they all have different
ldap servers. My problem is that we identify each client with their
login in remedy(for the most part) but some cases this is
not true. All of our base client accounts are pulled from HR and a
is attached to the login name. Problem is I cannot use the
login from ldap directly. I need to strip off the then
identify the user or let them type in there login name without the
but map it to the correct login name in the system.

I also need to be able to maintain the ability for the users to submit
tickets and modify these tickets without using a licenses. I have not
used the ldap interface much is there a good way to manipulate the
interface so that I can use the authentication of ldap and still
maintain my format of login and also maintain the submitter
priviledges for modification without a licenses (floating).

Darrel


UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org)

This KM article is quiet interesting.
But is there a way to get it vise versa?
The login shall be the domain account but in the ARS an alias shall be used.
E.g. I login with "smith" and when I use the $USER$ variable in ARS I would get "Will Smith"

Joerg
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG]On Behalf Of Grooms, Frederick W
Sent: Tuesday, November 08, 2005 11:42 PM
To: arslist@ARSLIST.ORG
Subject: Re: LDAP mapping


Check out the Remedy knowledge base article which
talks about the Authentication Login Name.

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Darrel Fossett
Sent: Tuesday, November 08, 2005 4:09 PM
To: arslist@ARSLIST.ORG
Subject: LDAP mapping

We have a multi-client environment. I am connecting remedy with LDAP of
our base company but none of the rest becuase they all have different
ldap servers. My problem is that we identify each client with their
login in remedy(for the most part) but some cases this is
not true. All of our base client accounts are pulled from HR and a
is attached to the login name. Problem is I cannot use the
login from ldap directly. I need to strip off the then
identify the user or let them type in there login name without the
but map it to the correct login name in the system.

I also need to be able to maintain the ability for the users to submit
tickets and modify these tickets without using a licenses. I have not
used the ldap interface much is there a good way to manipulate the
interface so that I can use the authentication of ldap and still
maintain my format of login and also maintain the submitter
priviledges for modification without a licenses (floating).

Darrel


UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org)


UNSUBSCRIBE or access ARSlist Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org)