Re: [rt-users] Assets RT 4.4.0
On 27 January 2017 at 08:59, Dunbar, Brian wrote: > When I set the owner. I could not set the Company it would only let me pick > a domain account This is a "glass half empty" solution but it might be of some use. Create a User to represent "the Company" Only fill in the username and Real Name fields Eg Username acme-ltd Real name Acme Ltd (An alternative for the Username of a "Company as User" is to use its FQDN, so acme.ltd) then make that "Company as User" Username the Owner of the Asset The "Real Name" should be visible in the Owner field on an Asset display page, and the link underneath it will take you to the User Summary page from where, selecting Edit, allows you to see the username, which is the thing you will probably need to see. When you come to search, be aware that, as the Assets search code stands, it won't autocomplete as you type, say, a c m e - l t d nor does it appear to handle wildcards, eg, acme% and nor does it appear to allow a search by "Real Name" but, if you can recall what the username is (so choose a scheme that is easy to recall !), typing it in in full should give you a string in the Owner field of the Search page that wil list all assets owned by that "Company as User" As I suggest, it's not exactly what you want, but part of the way there and, more importantly, as the Assets code develops so as to allow for better searches, your RT structure should be close to what you want, ie., a Company "thing" in the Owner.field.
[rt-users] Queues Categories and Custom Fields
Hi, I am just setting up a new install of RT and configuring Queues and Custom Fields and I am curious about best practices for doing this. For a given Queue, I would like to be able to define a Category for that Queue and then have specific Custom Fields based on the Queue -> Category. Is this possible? For instance for the "Helpdesk" queue, I could have 10 / 20 Categories that each have a different set of Custom Fields. I would rather not have a queue for each Category. Any advice appreciated. Thanks Spence -- View this message in context: http://requesttracker.8502.n7.nabble.com/Queues-Categories-and-Custom-Fields-tp63414.html Sent from the Request Tracker - User mailing list archive at Nabble.com.
Re: [rt-users] rt-mailgate in lab environment stopped working
Ok; I figured out what it is but I don't know why. "Time Management for System Administrators" - page 30 "Some general advice" - #7 - "The strangest problems often turn out to be misconfigured DNS." If I use the IP address for the server versus the FQDN, tickets flow in perfectly. If I use the FQDN of the server, it breaks. It's bizarre: DNS appears to be functioning properly in the test environment, but clearly based on this discovery it isn't. I'll consider this "solved" as this is more than likely my own d#mn fault. Stephen Cena Senior Systems Administrator Quality Vision International, Inc. Phone: (585) 544-0450 x300 To notify helpdesk: http://helpdesk.ogp.qvii.com or email: hd-gene...@qvii.com To report email issues: postmas...@qvii.com
Re: [rt-users] RT::User::ExternalAuthId Unimplemented in RT::Record
I also has not imported my groups. Daniel Burchfield - Senior IT Systems Administrator 1590 University Avenue Dubuque, IA 52001 Office 563-588-8748 ext. 1001 Toll Free 888-884-6331 ext. 1001 Office (direct): 563-293-8060 Mobile 563-564-7074 The information contained in this message is confidential and intended for the addressee only. If you have received this message in error, or there are any problems, please notify the sender immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. -Original Message- From: Daniel Burchfield Sent: Tuesday, February 7, 2017 9:15 AM To: 'Alex Vandiver' Cc: rt-users@lists.bestpractical.com Subject: RE: [rt-users] RT::User::ExternalAuthId Unimplemented in RT::Record That got rid of the error. Thanks. Now I am having trouble getting RT to check active directory for passwords. Is there something else I need to add to my config? Plugin('RT::Extension::LDAPImport'); Plugin('RT::Authen::ExternalAuth'); # Uncomment for debug #Set($LogToSyslog, 'debug'); Set( $CommentAddress, 'ithelpd...@mydomain.com' ); Set( $CorrespondAddress, 'ithelpdesk@ mydomain.com' ); Set( $DatabaseHost, 'localhost' ); Set( $DatabaseName, 'rt4' ); Set( $DatabasePassword, 'password' ); Set( $DatabasePort, '' ); Set( $DatabaseType, 'mysql' ); Set( $DatabaseUser, 'srv_rtir' ); Set( $Organization, '' ); Set( $OwnerEmail, 'ithelpdesk@ mydomain.com' ); Set( $SendmailPath, '/usr/sbin/sendmail' ); Set( $WebDomain, 'tracker. mydomain.local' ); Set( $WebPort, '8080' ); Set( $rtname, 'Medone-Tracker' ); # to fix that annoying error that the sites dont match Set(@ReferrerWhitelist, qw(tracker. mydomain.local:8080)); # LDAP Authentication Set( @Plugins, qw(RT::Extension::LDAPImport)); Set( @Plugins, qw(RT::Authen::ExternalAuth)); # LDAP user import Set($LDAPHost,' mydomain.local'); Set($LDAPUser, ' mydomain \LDAPUser'); Set($LDAPPassword, 'password'); Set($LDAPBase, 'CN=Users,DC= mydomain,DC=local'); Set($LDAPFilter, '(&(objectCategory=person))'); Set($LDAPMapping, { Name=> 'sAMAccountName', EmailAddress=> 'mail', Organization=> 'department', RealName=> 'cn', NickName=> 'givenName', Gecos => 'sAMAccountName', WorkPhone => 'telephoneNumber', MobilePhone => 'mobile', Address1=> 'streetAddress', City=> 'l', State => 'st', Zip => 'postalCode', Country => 'co' }); Set($LDAPCreatePrivileged, 1); Set($LDAPUpdateUsers, 1); ## LDAP GROUP IMPORT AND MAPPINGS Set($LDAPGroupMapping, {Name=> 'cn', Member_Attr => 'member', Member_Attr_Value => 'dn'}); #OU/basedn location of groups Set($LDAPGroupBase, 'ou=users,dc= mydomain,dc=local'); # LDAP GROUP FILTERING Set($LDAPGroupFilter, '(|(cn=Domain Users)(cn=Technical Operations)(cn=Management))'); ## LDAP Authentication # Use the below LDAP source for both authentication, as well as user # information Set( $ExternalAuthPriority, ["My_LDAP"] ); Set( $ExternalInfoPriority, ["My_LDAP"] ); # Make users created from LDAP Privileged Set( $UserAutocreateDefaultsOnLogin, { Privileged => 1 } ); # Users should still be autocreated by RT as internal users if they # fail to exist in an external service; this is so requestors (who # are not in LDAP) can still be created when they email in. Set($AutoCreateNonExternalUsers, 1); # Minimal LDAP configuration; see RT::Authen::ExternalAuth::LDAP for # further details and examples Set($ExternalSettings, { 'My_LDAP' => { 'type' => 'ldap', 'server' => '10.0.2.10', # By not passing 'user' and 'pass' we are using an anonymous # bind, which some servers to not allow 'base' => 'ou=Users,dc= mydomain,dc=local', 'filter' => '(objectClass=inetOrgPerson)', # Users are allowed to log in via email address or account # name 'attr_match_list' => [ 'Name', 'EmailAddress', ], # Import the following properties of the user from LDAP upon # login 'attr_map' => { 'Name' => 'sAMAccountName', 'EmailAddress' => 'mail', 'RealName' => 'cn', 'WorkPhone'=> 'telephoneNumber', 'Address1' => 'streetAddress', 'City' => 'l', 'State'=> 'st', 'Zip' => 'postalCode', 'Country' => 'co', }, }, } ); 1; Daniel
Re: [rt-users] RT::User::ExternalAuthId Unimplemented in RT::Record
That got rid of the error. Thanks. Now I am having trouble getting RT to check active directory for passwords. Is there something else I need to add to my config? Plugin('RT::Extension::LDAPImport'); Plugin('RT::Authen::ExternalAuth'); # Uncomment for debug #Set($LogToSyslog, 'debug'); Set( $CommentAddress, 'ithelpd...@mydomain.com' ); Set( $CorrespondAddress, 'ithelpdesk@ mydomain.com' ); Set( $DatabaseHost, 'localhost' ); Set( $DatabaseName, 'rt4' ); Set( $DatabasePassword, 'password' ); Set( $DatabasePort, '' ); Set( $DatabaseType, 'mysql' ); Set( $DatabaseUser, 'srv_rtir' ); Set( $Organization, '' ); Set( $OwnerEmail, 'ithelpdesk@ mydomain.com' ); Set( $SendmailPath, '/usr/sbin/sendmail' ); Set( $WebDomain, 'tracker. mydomain.local' ); Set( $WebPort, '8080' ); Set( $rtname, 'Medone-Tracker' ); # to fix that annoying error that the sites dont match Set(@ReferrerWhitelist, qw(tracker. mydomain.local:8080)); # LDAP Authentication Set( @Plugins, qw(RT::Extension::LDAPImport)); Set( @Plugins, qw(RT::Authen::ExternalAuth)); # LDAP user import Set($LDAPHost,' mydomain.local'); Set($LDAPUser, ' mydomain \LDAPUser'); Set($LDAPPassword, 'password'); Set($LDAPBase, 'CN=Users,DC= mydomain,DC=local'); Set($LDAPFilter, '(&(objectCategory=person))'); Set($LDAPMapping, { Name=> 'sAMAccountName', EmailAddress=> 'mail', Organization=> 'department', RealName=> 'cn', NickName=> 'givenName', Gecos => 'sAMAccountName', WorkPhone => 'telephoneNumber', MobilePhone => 'mobile', Address1=> 'streetAddress', City=> 'l', State => 'st', Zip => 'postalCode', Country => 'co' }); Set($LDAPCreatePrivileged, 1); Set($LDAPUpdateUsers, 1); ## LDAP GROUP IMPORT AND MAPPINGS Set($LDAPGroupMapping, {Name=> 'cn', Member_Attr => 'member', Member_Attr_Value => 'dn'}); #OU/basedn location of groups Set($LDAPGroupBase, 'ou=users,dc= mydomain,dc=local'); # LDAP GROUP FILTERING Set($LDAPGroupFilter, '(|(cn=Domain Users)(cn=Technical Operations)(cn=Management))'); ## LDAP Authentication # Use the below LDAP source for both authentication, as well as user # information Set( $ExternalAuthPriority, ["My_LDAP"] ); Set( $ExternalInfoPriority, ["My_LDAP"] ); # Make users created from LDAP Privileged Set( $UserAutocreateDefaultsOnLogin, { Privileged => 1 } ); # Users should still be autocreated by RT as internal users if they # fail to exist in an external service; this is so requestors (who # are not in LDAP) can still be created when they email in. Set($AutoCreateNonExternalUsers, 1); # Minimal LDAP configuration; see RT::Authen::ExternalAuth::LDAP for # further details and examples Set($ExternalSettings, { 'My_LDAP' => { 'type' => 'ldap', 'server' => '10.0.2.10', # By not passing 'user' and 'pass' we are using an anonymous # bind, which some servers to not allow 'base' => 'ou=Users,dc= mydomain,dc=local', 'filter' => '(objectClass=inetOrgPerson)', # Users are allowed to log in via email address or account # name 'attr_match_list' => [ 'Name', 'EmailAddress', ], # Import the following properties of the user from LDAP upon # login 'attr_map' => { 'Name' => 'sAMAccountName', 'EmailAddress' => 'mail', 'RealName' => 'cn', 'WorkPhone'=> 'telephoneNumber', 'Address1' => 'streetAddress', 'City' => 'l', 'State'=> 'st', 'Zip' => 'postalCode', 'Country' => 'co', }, }, } ); 1; Daniel Burchfield - Senior IT Systems Administrator 1590 University Avenue Dubuque, IA 52001 Office 563-588-8748 ext. 1001 Toll Free 888-884-6331 ext. 1001 Office (direct): 563-293-8060 Mobile 563-564-7074 The information contained in this message is confidential and intended for the addressee only. If you have received this message in error, or there are any problems, please notify the sender immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. -Original Message- From: Alex Vandiver [mailto:a...@chmrr.net] Sent: Thursday, February 2, 2017 11:16 PM To: Daniel Burchfield Cc: rt-users@lists.bestpractical.com Subject: Re: [rt-users] RT::User::ExternalAuthId Unimplemented in RT::Record On Thu, 2 Feb 2017 19:59:47
[rt-users] Configuration problem with Charts
Hi All, I'm having problems while trying to enabling Charts. I went through the following guide to enable it: https://docs.bestpractical.com/rt/4.4.1/charts.html But I'm still getting the "Graphical charts are not available" message on the Charts page. The GD dependencies are OK. I'm using RT 4.2.12 on CentOS Linux release 7.2.1511 What did I missed? Can anyone help in this issue? Thanks, Eszter
[rt-users] rt-mailgate in lab environment stopped working
Thomas - You are correct. It wouldn't be so bad if the RT site wasn't working. If I use the exact same address I use for the web server in the rt-mailgate scripts it fails. If I put that address into a web browser, I can use the system as expected. I'm trying to figure out what the "disconnect" is now between rt-mailgate and the server. Well, that error message is pretty clear ? when fetchmail tries to spawn rt-mailgate, that process can?t connect to RT. You should replace SERVER:80 in your fetchmailrc with the URL you?re using to connect to RT in your browser. HTH, Thoomas -- next part --