Hi,
We are using Passport authentication - RPS to setup a local site on Development environment. But we are facing issues after the credentials are entered in Liveid Login Page. The same setup has been done in production environment and it works fine.
The site is registered in msm.live.com and the appid/appsecretkey details are fetched from the registered site and placed in the web.config => <appsettings> section in 14 hive folder "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\SecurityToken"
<add key="WLA_ApplicationAlgorithm" value="wsignin1.0" />
<add key="WLA_ApplicationId" value="" />
<add key="WLA_ApplicationKey" value="" />
<add key="WLA_ProfileList" value="LiveID" />
<add key="WLA_ProfileSiteUrl" value="" />
<add key="SecutiryTokenPassword" value="" />
The applicationid and applicationkey values can be fetched from msm but we are not sure on the details about SecurityTokenPassword. Could you please let us know what is the significance of this key in appsettings.
Also as part of Site registration we have to upload a certificate to msm.live.com. Would like to understand about how this certificate will help in the authentication process as we are not provided with any certificate for the setup.
Thanks & Regards,
Nethra
We have a local site, set up on the Development Integration environment on that internal MS network.
We have been trying to set up the Passport Authentication on that.
Have registered the site on msm.live-int.com
Added the relevant details[Site ID etc.] in the rpserver.xml
When I try siging in, it should ideally navigate to https://login.live-int.com/login.srf
With my Site ID and the Return URL passed on in the query string.
Instead, I am getting this error:
"Something went wrong and we can't sign you in right now. Please try again later."
I am not sure what other details, need to be added.
Please guide.
Nethra
I am getting tired of this. help
[Server response: 535 5.2.1 Login to your account via a web browser to verify your account. code(535) ]
For SMTP, Gandi support ports 25, 465 (SSL) and 587. If neither 25 nor 587 (with authentication) is working, try 465. In this case, you should specify My server requires authentication on the Servers tab of the account's properties sheet. Click the Settings button, select Log on using and enter the username and password for the account.
On the Advanced tab, change the outgoing (SMTP) port to 465 and select This server requires a secure connection (SSL).
Close down WLMail and wait a few minutes before re-launching and sending a test message. Please post back with any new error message.
I have tried all the outgoing server port options: 25, 465(SSL) and 587. When I first switched to 587 outgoing mail worked for a short time ,and then it went back to not being able to send. I can receive and there is no problem with my ISP. I am pulling my hair out!
Split from another thread 
Recent Comments