
| Key: |
SEC-130
|
| Type: |
Improvement
|
| Status: |
Closed
|
| Resolution: |
Won't Fix
|
| Priority: |
Major
|
| Assignee: |
Luke Taylor
|
| Reporter: |
Luke Taylor
|
| Votes: |
0
|
| Watchers: |
2
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
This can probably be done using a specific authenticator implementation or by extending the existing BindAuthenticator.
|
|
Description
|
This can probably be done using a specific authenticator implementation or by extending the existing BindAuthenticator. |
Show » |
|
[quote]
I've heard of two "alternative" pseudo-DN syntaxes supported by AD. One
is "username@domain" and the other is "domain\username".
I think you can try binding with either of these using the existing
BindAuthenticator. If the user types in the entire name, you could have:
<property name="userDnPatterns">
<list>
<value>{0}</value>
</list>
</property>
or if they only type in the username part, you could use something like
<property name="userDnPatterns">
<list>
<value>{0}@mycompany.com</value>
<!-- and/or -->
<value>domain\{0}</value>
</list>
</property>
[/quote]
Anthony Geoghegan's response:
[quote]
I've tested both:
<value>{0}@mycompany.com</value>
<!-- and/or -->
<value>domain\{0}</value>
And they work with Active Directory 2003. The top one is of special
interest as this is the Kerberos service principal name.
[/quote]
User's can of course also bind with a full DN directly.