the c library doesn't seem to understand the insert_token string. ./utamghadm -s /opt/SUNWutref/amgh/utamghref_allkeys_script solved my problem.
On Tue, Feb 9, 2010 at 4:45 PM, Patrick <[email protected]> wrote: > Hi i'm testing amgh aswell. > > I notice using unregistered cards and using token= instead of insert_token= > works just fine. > registering the tokens and using insert_token does not. > > i'm on srss 4.2 x86. > > any ideas ? > > > > On Tue, Feb 9, 2010 at 11:31 AM, Joerg Barfurth <[email protected]> wrote: > >> Scott L Riggen schrieb: >> >> >> I'm returning host="hostname" with my script when you pass it insert_token >>> >>>> Both username and host are optional, but it's not very interesting if >>>> you don't return at least one of them :) >>>> >>> >>> >> Switching is still busted. When I put in my two test cards (both >>> pointing at hosts in different FOGs I still stay on whatever host the sunray >>> happens to connect to when it gets back it's dhcp answer. >>> the only thing I see in messages is that amgh is yes but that it has >>> nothing in the reply. The DETAILS section shows Details=AMGH lookup library >>> did not provide any target AMGH hosts, AMGH_Target=*NONE* >>> Also the token says user.1265220350-7053 (what is this......?) >>> >>> Feb 8 15:21:55 bender.cesa.opbu.xerox.com utauthd: [ID 118791 user.info] >>> Worker2 NOTICE: MTU = 1500 >>> Feb 8 15:21:56 bender.cesa.opbu.xerox.com utdtsession: [ID 702911 >>> user.info] Add (5,user.1265220350-7053,normal) >>> Feb 8 15:21:58 bender.cesa.opbu.xerox.com utauthd: [ID 988467 user.info] >>> Worker2 NOTICE: SESSION_OK user.1265220350-7053 >>> Feb 8 15:22:00 bender.cesa.opbu.xerox.com dtlogin[2736]: [ID 118685 >>> user.info] pam_sunray_amgh::[DPY=5] AMGH_SUMMARY: >>> token=user.1265220350-7053, username=, >>> AMGH_Done?=NO(Local Session), Details=AMGH lookup library did not >>> provide any target AMGH hosts, AMGH_Target=*NONE* >>> Feb 8 15:22:02 bender.cesa.opbu.xerox.com utauthd: [ID 140345 >>> user.info] Worker4 NOTICE: DISCONNECT IEEE802.0003ba3c12dd, >>> user.1265220350-7053 token removed >>> >>> >> So this looks as if AMGH thinks everything is right, but your script does >> not return the expected values. >> >> You could try to instrument your script, either with selected echo >> statements or with 'set -x', and redirect the results of that to a special >> log file (or just to /tmp/amghlog$$), so that you can see what you script >> actually does. >> >> HTH >> >> - Jörg >> >> _______________________________________________ >> SunRay-Users mailing list >> [email protected] >> http://www.filibeto.org/mailman/listinfo/sunray-users >> > >
_______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
