Re: [rt-users] Upgrading from 4.0.8 to 4.2.1 missing dashboards
Anyone have any suggestions on this? I've tried restoring my database and running the make upgrade-database again but the same thing happens. It seems like my user loses all permissions, etc? I even tried enabling the root user and it's the same thing, just a list of open tickets, no options, etc. Thanks, Chris Black IT Manager Gourmet Trading HelpDesk: 310-216-1234 chr...@gourmettrading.net On Thu, Nov 28, 2013 at 11:48 AM, Chris Black wrote: > Hi everyone, > > I just upgraded from 4.0.8 to 4.2.1 this morning and when I log in with my > username which was full admin. When I log in now, I am only seeing my list > of "open tickets". I can't find any dashboard options, admin options, etc. > > I did run make upgrade-database and there were no errors. > > Did I miss part of the upgrade process? > >
[rt-users] AD domains with RT::Authen::ExternalAuth
At the moment using RT::Authen::ExternAuth for LDAP authentication to Active Directory it's not possible to use DOMAIN\user syntax. This is at odds with much of the other (Windows based) infrastructure we use, and it confuses our users. Until recently we've been trying to mitigate the issue with a message that reminds people to omit the domain part, but it's not a clean solution and has been bugging me. I've finally got around to making some changes to RT::Authen::ExternalAuth that allows me to define the Windows domain. This isn't a true Forest/Trust model but it's sufficient for us. The change is, I believe, backwards compatible with existing installations as the domain can be an optional component. Examples: "DOMAIN\user" - succeeds if DOMAIN is required and matches, and user is authenticated in LDAP "user" - succeeds if DOMAIN is optional, and user is authenticated in LDAP "OTHERDOMAIN\user" - fails if DOMAIN is required but does not match "DOMAIN\otheruser" - fails if DOMAIN matches, but otheruser is not authenticated in LDAP In order to support this I've added three new configuration elements in RT_Site_Config.pm, settable per LDAP configuration section: 'ad_domain_prefix' => 'DOMAIN',# is case insensitive 'ad_domain_required' => 'no',# { 'yes' | 'no' } 'ad_domain_separator' => '\\',# split domain\user with this character Are the patches something that would be useful to share here? I've tried emailing the contact in the RT::Authen::ExternalAuth but heard nothing back. Chris smime.p7s Description: S/MIME Cryptographic Signature
[rt-users] changing Organization
I would like to change our Organization name to avoid confusion with another RT instance? Does anyone have a script to fixup the RT database so that I can change the Organization name without breaking the RT ticket links?