Bob Doolittle wrote: > David Markey wrote: >> Bob Doolittle wrote: >> >>> Another way to manage this, which was available in 4.0 and would also >>> work in 4.1 with RHA disabled is to use AMGH. The most common use of >>> AMGH is to redirect users to specific FOGs, but it can also be used >>> simply to set a username based on environmental params such as a >>> smartcard ID. Places to start learning about AMGH are the Admin Guide, >>> the man pages utamghadm(1) and ut_amgh_script_interface(3), the >>> reference code in /opt/SUNWutref/amgh/*script, and my blog >>> http://blogs.sun.com/bobd. >>> >> Yes i might put payflex ids -> username mappings in LDAP and use AMGH to >> fill in the required username on each connect. would this be exactly >> what you're suggesting? >> > > Yep :). Or rdist your file that contains the mappings today, and use > the file. > > But usernames should already be carried along with a utswitch even > with smartcards if you didn't use "-D" as a utpolicy option (or enable > "Direct Session Access" via the admin browser interface). Can you send > me the output of the "utpolicy" command? If there is a bug here, we > should fix it. > > -Bob > > _______________________________________________ > SunRay-Users mailing list > [email protected] > http://www.filibeto.org/mailman/listinfo/sunray-users Oh i forgot to mention that im using utswitch in a custom kiosk(the one i talked about about a month back in another thread). So therefore utswitch will never know the username to pass, but i wanted to specify it using my payflex id->userid pair file.
_______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
