#308 Authentication request failed entered and stored passwords do not match.

[Sean Johnston]

I've looked at all of the other tickets

I can't seem to log in even after updating to SIPE 1.20.1. Getting

connection: Connection error on 0x55d4fd5a4060 (reason: 2 description: Web ticket request to https://XXXXXXXX.infra.lync.com:443/CertProv/CertProvisioningService.svc failed
(The entered and stored passwords do not match.))

Tried with both login populated with myname@mycompany.com and being blank. User agent is

UCCAPI/15.0.4420.1017 OC/15.0.4420.1017 (Microsoft Lync)

and using TLS-DSK authentication scheme.

Log pastebin: http://pastebin.com/Gjc3rZhM

Thanks for any help, and let me know if I need to provide anything else!

[Stefan Becker]

There is nothing wrong on the SIPE side, the username and password just aren't accepted by the Microsoft login service,

Maybe your email address and SIP account names are different?

I assume that this is a Offcie 365 account. Have you tried to login using the same username and password n the Office 365 web pages?

Closing as INVALID

[Sean Johnston]

Thanks a bunch for taking a look.

Gosh, that's frustrating. It's an Office 365 account for work. I can go onto office365.com, click Sign In -> Work, school, or university, which redirects to login.microsoftonline.com, and successfully sign in perfectly fine.

[Sean Johnston]

You know--whenever I try and log in at office365.com at a place other than work, I end up needing to provide two-factor authentication in the form of a text message. Does this make any difference?

[Stefan Becker]

Lync does not support MFA and SIPE has support to ignore MFA (see Feature #76 for a detailed discussion):

• MFS requires ADFS setup
• ADFS fails in MFA case
• after ADFS fails SIPE falls back to FedBearer authentication, i.e. it goes to login.microsoft.com

Your log shows that no ADFS is configured for that SIP URI, so we go to FedBearer authentication immediately.

To repeat: I'm guessing that your email, account and/or Lync account names are different. If you are trying to login with your email address instead of the lync account name then the password won't match.

[Sean Johnston]

Thanks for your help. It turned out that I was using the correct username, but we have some specific application passwords that needed to be used instead of the general password.

[Stefan Becker]

Out of curiosity: where did you get this application password? From your admin or from your Office 365 account page? If the latter, where?

[Sean Johnston]

We have a text file in the root directory of our Office365 OneDrive that details the password. I'm not sure if our IT department put it there or if it was generated by Office365 somehow?

[serkan]

I have a similar issue as well for me the problem is even more weird, I get http://dummystsurl.microsoftonline.com/dummyurl as STSAuthURL full logs (anonymized) attached

[serkan]

Sorry posted at wrong place I'm gonna re-post this in the forum topic.