|
Home > Archive > IIS Server Security > June 2007 > Can't get advanced digest authentication working
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Can't get advanced digest authentication working
|
|
|
| Any pointers on what I've missed would be great:
Windows 2003 IIS, domain functional level is windows 2003 (forest still at
2000).
Have set UseDigestSSP at the w3svc level to 1 via
adsutil.vbs w3svc/useDigestSSP1 and checked with Metabase Explorer tool that
correctly set.
Set the website to use only digest authentication via IIS manager and set
realm to fqdn of domain.
Restarted iis services, changed password on user account but get access
denied errors on IE6 page request (if use other authentication methods the
page loads ok).
I've seen one reference that the MD5 password hash may be stored in AD in
the altsecurityparameter attribute for a user but this isn't populated in
adsiedit on a password reset.
Thanks
David
| |
| WenJun Zhang[msft] 2007-06-08, 7:24 am |
| Hi David,
First of all, is the server a member of Windows 2003 domain? Currently only
Windows 2003 domain supports Advanced Digest authentication because only
Windows 2003 domain controller stores the digest hash. Please refer to:
824032 Digest authentication and Advanced Digest authentication in Windows
Server 2003
http://support.microsoft.com/defaul...kb;EN-US;824032
Thanks.
Sincerely,
WenJun Zhang
Microsoft Online Community Support
========================================
==========
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at:
http://msdn.microsoft.com/subscript...t/default.aspx.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.
| |
|
| Hi there - yes it is a member server.
As per your Q article a user should have the password hash stored in
AltSecID . I assume this is the same as altsecurityidentities as shown in
adsiedit (we don't have altsecid listed). How do we troubleshoot this - or
is this an AD group question?
Thanks
David
""WenJun Zhang[msft]"" <wjzhang@online.microsoft.com> wrote in message
news:vmpdzzaqHHA.3656@TK2MSFTNGHUB02.phx.gbl...
> Hi David,
>
> First of all, is the server a member of Windows 2003 domain? Currently
> only
> Windows 2003 domain supports Advanced Digest authentication because only
> Windows 2003 domain controller stores the digest hash. Please refer to:
>
> 824032 Digest authentication and Advanced Digest authentication in Windows
> Server 2003
> http://support.microsoft.com/defaul...kb;EN-US;824032
>
> Thanks.
>
> Sincerely,
>
> WenJun Zhang
>
> Microsoft Online Community Support
>
> ========================================
==========
>
> Get notification to my posts through email? Please refer to:
> http://msdn.microsoft.com/subscript...ault.aspx#notif
> ications.
>
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at:
>
> http://msdn.microsoft.com/subscript...t/default.aspx.
>
> ========================================
==========
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
| |
|
| From Microsoft Windows XP/2003 Security Target paper, 2005:
http://niap.bahialab.com/cc-scheme/st/st_vid4025-st.pdf
'However, in Windows Server 2003 TOE, the AD extended schema properties
ensures that every newly created user account automatically has the Digest
authentication password hashed and stored as a field in the "AltSecId"
property of the user object.'
Also altsecid and atsecurityidentities appear to be identical?
http://www.google.co.uk/search?hl=e...dentities&meta=
Our problem is that when a new domain account is created
altsecurityidentities is not populated for that user.
Thanks
David
"David" <idstechnet@noemail.noemail> wrote in message
news:et069LbqHHA.4108@TK2MSFTNGP06.phx.gbl...
> Hi there - yes it is a member server.
> As per your Q article a user should have the password hash stored in
> AltSecID . I assume this is the same as altsecurityidentities as shown in
> adsiedit (we don't have altsecid listed). How do we troubleshoot this -
> or is this an AD group question?
> Thanks
> David
>
> ""WenJun Zhang[msft]"" <wjzhang@online.microsoft.com> wrote in message
> news:vmpdzzaqHHA.3656@TK2MSFTNGHUB02.phx.gbl...
>
>
|
|
|
|
|