Dan Delaney wrote: > > I believe I have pinpointed where this error is coming from. User1 is more > of a management account (mine) which allows full access to everything, while > user2 is a simple "mailbox only" account. What appears to be happening is > that our OpenVMS radius server is allowing user1 because it will permit the > interactive-logon, but failing user2 because it does not allow > interactive-logins. When we manually allowed these logins for user2, it went > through without any problems.
OK. I took a look at pam_radius_auth. It does appear to implement session management functions, contrary to my expectations (oh, those crazy expectations). Try removing the "account" and "session" lines from the pam configuration file, and see if you still need to change things on your radius server. > So my next issue is selectively choosing what service type is used for which > protocol. I Saw a patch from 2000 which added a service_type function to > pam_radius_auth, but it does not seem to be in the current release. I Was > going to try to manually patch and recompile. (copying and pasting the patch > didn't seem to work right) It'd be more maintenance if you had to go that way, but I'm curious what works. Let me know. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
