Some other options are using AREA LDAP to authenticate unregistered users. You can use this in conjunction with cross reference blank password. This will allow all users to authenticate and login to Remedy with read/public access with no need for a user record. For all support staff you would setup a user record and assign appropriate licenses/groups. You also have the option to have AREA LDAP handle all licensing and group assignments, so that you don't have to worry about managing users in Remedy. -----Original Message----- From: Thad Esser [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 7, 2006 03:08 PM To: [email protected] Subject: Re: Users - Person Information
** Not really, but I'm pretty sure I've got it. :-) I didn't mention the Blank Password because that presumes a registered user in the user form, and the clarification I sought was in regards to what conditions would need to be present to allow you to not have a user record, addressing David's question #1. Thanks, Thad "Argue for your limitations, and sure enough, they're yours."-- Richard Bach "Rick Cook" <[EMAIL PROTECTED]> Sent by: "Action Request System discussion list(ARSList)" <[email protected]>11/07/2006 10:47 AMPlease respond to [email protected] To [EMAIL PROTECTED] Subject Re: Users - Person Information ** Under those specific circumstances, you're right, Thad, though the blank password setting assumes, and is looking for, a User record (which could be a generic one, I suppose). If a user will be logging in as him/herself, and require a Remedy license of any kind, they will need a user record. Otherwise, they will not. That clearer? On 11/7/06, Thad Esser <[EMAIL PROTECTED]> wrote: ** Rick, Can you clarify this statement: "...if the user will log on to Remedy for anything, they need a login/pw, which means a User record." If the person is only using Remedy Requester (isn't a support person in any way) and you have Submitter Mode Locked, Allow Guest Users, and Authenticate Unregistered Users all set, then would those people still need a user record? What other issues (other than the lack of default notification issue) crop up with these settings? Thanks, Thad "Argue for your limitations, and sure enough, they're yours."-- Richard Bach "Rick Cook" <[EMAIL PROTECTED]> Sent by: "Action Request System discussion list(ARSList)" < [email protected]>11/07/2006 09:11 AM Please respond to [email protected] To [EMAIL PROTECTED] Subject Re: Users - Person Information ** David, Basic difference is that if the user will log on to Remedy for anything, they need a login/pw, which means a User record. If they will only call the Help Desk, they only need a people record for reporting and convenience purposes. One would generally not want to have all of one's people in the User form, as performance can be an issue. Rick On 11/7/06, David Yearsley < [EMAIL PROTECTED]> wrote: ** ITSM 6.0 ARServer 6.00.03 We are in the process of expanding our use of Remedy ITSM suite and have several questions. If you add someone from the "Configuration Manager" there is a record created in both the user and shr:people form. If you add someone from a helpdesk ticket the only record created is in the shr:people form. (Unless something we changed is preventing the user record creation.) We have researched the questions below and have conflicting viewpoints. We just want to find a general idea of how other organizations are handling this issue. Questions: 1. Should there be a record in the User form for every record in the shr:people form? (Is this a company decision?) 2. If we decide to have all shr:people information in the user are there any issues? (Is this a performance problem - We have 15000 people?) 3. If a User Record should be created from when a person is added from a Help Desk ticket, does anyone know what programming creates the user record? (Ours could be missing. I have been checking the logs and cannot find any programming that would create a user record.) 4. Is there a best practices for determining who should be in the User form and the People form? __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ ***IMPORTANT NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited. Nothing in this email, including any attachment, is intended to be a legally binding signature.*** __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
