Authentication Error
Authenticating failed due to the following error: We already have a registered user with this email address. Log in to connect your GitHub account.
Related
Error Messages: When I am trying to connect DocuSign with salesforce, I am getting error "Web service callout failed: Unable to parse callout response. Apex type not found for element turnTLSv11Off"
Install DocuSign for Salesforce from App Exchange
Go to DocuSign Admin tab
Connect DocuSign demo account. It will get connected successfully.
Connect DocuSign with Salesforce . Enter Salesforce username and credentials
Error messages : Web service callout failed: Unable to parse callout response. Apex type not found for element turnTLSv11Off
This is a known issue that is being investigated. The current workaround is to configure SF Admin credentials in Connect (Log in to the DocuSign Web Console > Settings > Connect > Salesforce > Reconfigure login). As the previous step is completed, that'll get things linked from both sides.
I am trying to log in to Query Editor in the Azure online portal. For some reason I have the below message under the Active Directory authentication area:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
I can still log in using SQL server authentication and I can log in using SSMS from my local machine using Active Directory credentials.
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
Can someone surmise why I am getting this error?
If you have set the AD admin account like this tutorial Configuring an Active Directory (AD) administrator do:
When we using the Query Editor(preview), it will shows your AD authentication account:
Just click the 'continue as **#****.com', Query Editor will login your database with AAD authentication.
Hope this helps.
I have a release pipeline that deploy's a web application to an Azure App service. Everything was working, until I transferred the Azure subscription to another owner. It has been over 24 hours since the transfer has been completed and still getting the error.
I have granted myself Global Admin role.
Error(s):
Service connection creation operation failed
Failed to set Azure permission 'RoleAssignmentId: 380a3598-2863-4b12-b8e7-9e80d7d50125' for the service principal 'f0f249b2-2f4b-435b-b7d7-2d5a739b14a6' on subscription ID '834a2851-5d95-4e8e-9196-cb583f4fdb69': error code: Unauthorized, innner error code: InvalidAuthenticationTokenTenant, inner error message The access token is from the wrong issuer 'https://sts.windows.net/0fd08f18-29f8-479b-80d9-8d28b52bab6c/'. It must match the tenant 'https://sts.windows.net/b6ee8e7c-ae9f-4188-8654-65dbbbd2b302/' associated with this subscription. Please use the authority (URL) 'https://login.windows.net/b6ee8e7c-ae9f-4188-8654-65dbbbd2b302' to get the token. Note, if the subscription is transferred to another tenant there is no impact to the services, but information about new tenant could take time to propagate (up to an hour). If you just transferred your subscription and see this error message, please try back later. For troubleshooting refer to link.
Session Id: 0d012481-a910-4b74-981b-bffca782472d
I was able to resolve the issue by having my user removed from AD on the account that the subscription was transferred from.
I configured azure AD as an identity provider for my organization's application
as specified in the below blog
Bring your own app with Azure AD Self-Service SAML configuration
I created an application under activity directory and configured single signon (SAML2) for the same as below
SIGN ON URL
https://abc.xxxx.com/myapp/saml/ssoRequest?ticket=kcflmlmnpgg
ISSUER URL
https://abc.xxxx.com
REPLY URL
https://abc.xxxx.com/myapp/ssoResponse
whenever i try to access the application its redirecting the request to azure login. But I am getting a bad request error and its showing the below message
AADSTS50003: No signing key is configured.
Whenever I try to access my application, it is redirecting me to azure login page. It asks me to login , if I am not already logged in and after login the above error is thrown. If I am already logged in; the error is shown directly
Am I missing something in the configuration
The request was not signed. After sigining the request it started working.
I am receiving this error "AADSTS50001: is not registered for the account." when I log into my web app hosted in Azure Cloud. I am trying to log in using a different domain then the address my web app is linked too.
I added the e-mail address that I am trying to login with to the AAD of the domain name of the web app that I am accessing. I still got the error message.
Here is the full error message.
Additional technical information:
Correlation ID: 3411f3dd-a2c8-4412-9534-4d18123601bc
Timestamp: 2014-08-26 13:30:55Z
AADSTS50001: is not registered for the account.