i am confiuring federation between openam( opensso)( relying party) and ASFS 2.0( identity provider) using ws-federation. when i am trying to authenticate the user on the identity provider i am getting error 4625( error details below). the Kerberos.dll verison is 6.1.7600.16385. I donot know applying the hotfix http://support.microsoft.com/kb/2157973 will make any difference. Log Name: Security Source: Microsoft-Windows-Security-Auditing Date: 5/21/2011 4:12:56 AM Event ID: 4625 Task Category: Logon Level: Information Keywords: Audit Failure User: N/A Computer: infyadfs.infy.com Description: An account failed to log on. Subject: Security ID: NULL SID Account Name: - Account Domain: - Logon ID: 0x0 Logon Type: 3 Account For Which Logon Failed: Security ID: NULL SID Account Name: infy/administrator Account Domain: Failure Information: Failure Reason: Unknown user name or bad password. Status: 0xc000006d Sub Status: 0xc0000064 Process Information: Caller Process ID: 0x0 Caller Process Name: - Network Information: Workstation Name: NCO Source Network Address: - Source Port: - Detailed Authentication Information: Logon Process: NtLmSsp Authentication Package: NTLM Transited Services: - Package Name (NTLM only): - Key Length: 0 This event is generated when a logon request fails. It is generated on the computer where access was attempted. The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe. The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network). The Process Information fields indicate which account and process on the system requested the logon. The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases. The authentication information fields provide detailed information about this specific logon request. - Transited services indicate which intermediate services have participated in this logon request. - Package name indicates which sub-protocol was used among the NTLM protocols. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" /> <EventID>4625</EventID> <Version>0</Version> <Level>0</Level> <Task>12544</Task> <Opcode>0</Opcode> <Keywords>0x8010000000000000</Keywords> <TimeCreated SystemTime="2011-05-21T08:12:56.171963100Z" /> <EventRecordID>11232</EventRecordID> <Correlation /> <Execution ProcessID="504" ThreadID="2284" /> <Channel>Security</Channel> <Computer>infyadfs.infy.com</Computer> <Security /> </System> <EventData> <Data Name="SubjectUserSid">S-1-0-0</Data> <Data Name="SubjectUserName">-</Data> <Data Name="SubjectDomainName">-</Data> <Data Name="SubjectLogonId">0x0</Data> <Data Name="TargetUserSid">S-1-0-0</Data> <Data Name="TargetUserName">infy/administrator</Data> <Data Name="TargetDomainName"> </Data> <Data Name="Status">0xc000006d</Data> <Data Name="FailureReason">%%2313</Data> <Data Name="SubStatus">0xc0000064</Data> <Data Name="LogonType">3</Data> <Data Name="LogonProcessName">NtLmSsp </Data> <Data Name="AuthenticationPackageName">NTLM</Data> <Data Name="WorkstationName">NCO</Data> <Data Name="TransmittedServices">-</Data> <Data Name="LmPackageName">-</Data> <Data Name="KeyLength">0</Data> <Data Name="ProcessId">0x0</Data> <Data Name="ProcessName">-</Data> <Data Name="IpAddress">-</Data> <Data Name="IpPort">-</Data> </EventData> </Event>

On Sat, 21 May 2011 13:53:57 +0000, xxsdfe wrote: i am confiuring federation between openam( opensso)( relying party)?and ASFS 2.0( identity provider)?using ws-federation. when i am trying to authenticate the user on the identity provider i am getting error 4625( error details below). the Kerberos.dll verison is 6.1.7600.16385. I donot know applying the hotfix http://support.microsoft.com/kb/2157973?will make any difference. This isn't the correct forum for ADFS questions. It looks like while there's no specific ADFA forum the Directory Services forum is commonly used for ADFS questions: http://social.technet.microsoft.com/Forums/en-US/winserverDS/threads Paul Adare MVP - Identity Lifecycle Manager http://www.identit.ca There are two ways to write error-free programs; only the third one works.

AD FS questions can also be posted to the "claims based access platform" http://social.msdn.microsoft.com/Forums/en-US/Geneva/threadshttp://setspn.blogspot.com

issue resolved log in using UPN ( admin@abc.com)