Originally reported on Google Code with ID 246
What steps will reproduce the problem?
1. Configure a realm in Tomcat that authenticates e.g. user X
2. Deploy gitblit WAR on Tomcat
3. Authenticate user X via Tomcat (not via gitblit login)
4. Gitblit will NOT treat the session principal as a user
What is the expected output? What do you see instead?
It would be great if gitblit could auto-create a gitblit user for the authenticated
principal if no gitblit user with that user id exists yet.
Instead it seems that Gitblit resolves an unknown principal as a null UserModel and
effectively ignores the principal.
What version of the product are you using? On what operating system?
Gitblit v1.2.1, WAR edition, deployed on Tomcat 7 on Debian 7 ("wheezy").
Please provide any additional information below.
According to James Moger, the Ldap and Redmine user services will auto-create user
accounts based on successful authentication. The same approach could be used for servlet
container based authentication.
See the related conversation between me and James here:
https://groups.google.com/forum/?fromgroups#!topic/gitblit/iBJwfrzpSaI
Reported by oliver.doepner on 2013-05-25 23:49:18
Originally reported on Google Code with ID 246
Reported by
oliver.doepneron 2013-05-25 23:49:18