Hi Scott, Yep, the easiest thing to do would be to check out the trunk and make any additions (classes, tests, etc) that you may need and ensure the project builds. Then the best thing to do is to create a patch from the root of the codebase and attach that patch to a Jira issue.
Thanks! Les On Wed, Jan 5, 2011 at 10:19 PM, Scott Kub <[email protected]> wrote: > > Hey Les, > > I transferred the code over to my home computer now, so I can either start > working on integrating it into Shiro or I can give you the snippets I have. > Which way works best? > > If it's for me to checkout the source and add the code, is this still your > advice: > > The easiest thing to do is subclass the > > org.apache.shiro.realm.AuthorizingRealm and implement the > > 'doGetAuthenticationInfo' method (just return null for now for the > > remaining doGetAuthorizationInfo method). > > >> That method will give you an AuthenticationToken (probably a > > UsernamePasswordToken). You take that and use it to perform the > > Kerberos login. In other words, all integration to get this to work > > should stem from 'doGetAuthenticationInfo' only - you don't need to > > worry about anything else in Shiro. > > >> The question is - if you can contribute this, can you please post it > > as a .zip to Jira? As an ASF project, we can't accept anything that > > is not considered an ASL 2.0-compatible contribution. Posting to Jira > > acts as a provenance mechanism that allows us to accept code from the > > community. > > >> Perhaps the easiest thing to do is to create a new Maven module under > > the <project source root>/support directory and upload only that > > module to Jira. > > -- > View this message in context: > http://shiro-user.582556.n2.nabble.com/Gathering-Windows-logon-credentials-tp5272872p5894462.html > Sent from the Shiro User mailing list archive at Nabble.com.
