I installed a few days ago RT 3.0.2 and I find it really interesting.
After a few tests I started reading the mailing list, in order to get some
info about customization.
I need some help to perform a few steps:
CustomFields: I defined a few global custom fields, in order to let the
requestors insert some info about their tickets.
When I access RT via Web as a non-privileged user, I create a new ticket but
I can’t see the custom fields.
Is there some way to let the non staff people see those fields and to
insert/select the values?
WebExternalAutoInfo: I configured apache to auth users against an Active
Directory.
I would like also to use the autocreate feature, in order to have their
attributes up-to-date with our user data base.
I got some code from this mailing list: I modified the
INSTDIR/share/html/autohandler, where I invoked the
WebExternalAutoInfo subroutine, but I don’t know where to insert the
subroutine itself.
I would like to grant non privileged users the right to close their
tickets before they become “open”: in other words,
if the requestor find the solution by his way, I would permit him to close
his ticket.
WebExternalAutoInfo: I configured apache to auth users against an Active
Directory.
I would like also to use the autocreate feature, in order to have their
attributes up-to-date with our user data base.
I got some code from this mailing list: I modified the
INSTDIR/share/html/autohandler, where I invoked the
WebExternalAutoInfo subroutine, but I don’t know where to insert the
subroutine itself.
The only code I remember seeing on this mailing list about that, was
mine for rt2. It sounds like you’re using rt3, so that’s all wrong.
rt3 has it’s own auto-create-web-users thing. It’s a varible in the
config file. It will create users with a username and real name of
whatever apache sets REMOTE_USER to.
I create a couple patches that will give you something morally
equivlent to CanonicalizeWebUser, they’ll probably get added to apache
sometime. They can be found at http://rt3.fsck.com/Ticket/Display.html?id=2667
Hi Seph
thank you for your reply. I’m using rt3.0.2 for my test.
I suppose the right way is:
Set WebExternalAuth: let Apache look at Active Directory and set
$REMOTE_USER
Set WebFallbackToInternalAuth: let root (and only root for my purposes)
authenticate against internal db… He will fail ldap login and switch to
internal user db
Set WebExternalAuto: to let rt create/update users when loggin in
Interface/Web.pm: insert WebCanonicalizeInfo() and WebExternalAutoInfo()
with ldap code to do the right things…
/html/autohandler: insert your patch. I’m not sure I understand
WebExternalOnly and orig_user
The second, I suppose, is used to roll back to the prev user in the browser
context in some way
Stefano Congiu
-----Messaggio originale-----
Da: rt-users-admin@lists.fsck.com [mailto:rt-users-admin@lists.fsck.com] Per
conto di seph
Inviato: mercoledì 18 giugno 2003 5.49
A: Stefano Congiu
Oggetto: Re: [rt-users] Customize RT 3.0.2 for WebExternalAutoInfo and
CustomFields
WebExternalAutoInfo: I configured apache to auth users against an
Active Directory. I would like also to use the autocreate feature, in
order to have their attributes up-to-date with our user data base.
I got some code from this mailing list: I modified the
INSTDIR/share/html/autohandler, where I invoked the
WebExternalAutoInfo subroutine, but I don’t know where to insert the
subroutine itself.
The only code I remember seeing on this mailing list about that, was mine
for rt2. It sounds like you’re using rt3, so that’s all wrong.
rt3 has it’s own auto-create-web-users thing. It’s a varible in the config
file. It will create users with a username and real name of whatever apache
sets REMOTE_USER to.
I create a couple patches that will give you something morally equivlent to
CanonicalizeWebUser, they’ll probably get added to apache sometime. They can
be found at http://rt3.fsck.com/Ticket/Display.html?id=2667