Identity Server Login Error
I am trying to create a username and password for an external client to use. I am able to create the username and password through Manager and set permissions, however when I launch my site and click on Identity Server to log in I recieve the following error,
Server Error in '/Geocortex/IdentityServer' Application.
Invalid realm: http://thgis12ss11.mmm.ca/Geocortex/Essentials/Geocortex_Essentials_4.43/REST/security/callback
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.IdentityModel.Protocols.WSTrust.InvalidRequestException: Invalid realm: http://thgis12ss11.mmm.ca/Geocortex/Essentials/Geocortex_Essentials_4.43/REST/security/callback
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[InvalidRequestException: Invalid realm: http://thgis12ss11.mmm.ca/Geocortex/Essentials/Geocortex_Essentials_4.43/REST/security/callback] Thinktecture.IdentityServer.TokenService.Request.ValidateKnownRealm(RequestDetails details) +178 Thinktecture.IdentityServer.TokenService.TokenService.GetScope(ClaimsPrincipal principal, RequestSecurityToken rst) +315 System.IdentityModel.SecurityTokenService.Issue(ClaimsPrincipal principal, RequestSecurityToken request) +93 System.IdentityModel.Services.FederatedPassiveSecurityTokenServiceOperations.ProcessSignInRequest(SignInRequestMessage requestMessage, ClaimsPrincipal principal, SecurityTokenService sts, WSFederationSerializer federationSerializer) +354 Thinktecture.IdentityServer.Protocols.WSFederation.WSFederationController.ProcessWSFederationSignIn(SignInRequestMessage message, ClaimsPrincipal principal) +127 lambda_method(Closure , ControllerBase , Object[] ) +79 System.Web.Mvc.ReflectedActionDescriptor.Execute(ControllerContext controllerContext, IDictionary`2 parameters) +270 System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary`2 parameters) +39 System.Web.Mvc.Async.<>c__DisplayClass39.<BeginInvokeActionMethodWithFilters>b__33() +120 System.Web.Mvc.Async.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49() +452 System.Web.Mvc.Async.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49() +452 System.Web.Mvc.Async.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49() +452 System.Web.Mvc.Async.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49() +452 System.Web.Mvc.Async.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49() +452 System.Web.Mvc.Async.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49() +452 System.Web.Mvc.Async.<>c__DisplayClass37.<BeginInvokeActionMethodWithFilters>b__36(IAsyncResult asyncResult) +15 System.Web.Mvc.Async.<>c__DisplayClass2a.<BeginInvokeAction>b__20() +33 System.Web.Mvc.Async.<>c__DisplayClass25.<BeginInvokeAction>b__22(IAsyncResult asyncResult) +240 System.Web.Mvc.<>c__DisplayClass1d.<BeginExecuteCore>b__18(IAsyncResult asyncResult) +28 System.Web.Mvc.Async.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) +15 System.Web.Mvc.Controller.EndExecuteCore(IAsyncResult asyncResult) +53 System.Web.Mvc.Async.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) +15 System.Web.Mvc.<>c__DisplayClass8.<BeginProcessRequest>b__3(IAsyncResult asyncResult) +42 System.Web.Mvc.Async.<>c__DisplayClass4.<MakeVoidDelegate>b__3(IAsyncResult ar) +15 System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +606 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +288
Anyone have any idea as to what this is or what is causing it?
0
-
Hi Stephanie,
To fix this issue, you can try re-running the Post Installer. Just make sure the host names are correct with the correct protocol (HTTP/HTTPS) and make sure that SSL is enabled if your services are running over HTTPS.
Once you check those settings, you can hit finish to update your configuration and reload the viewer to see if that fixes the issue.
Regards,
Carmen0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
1 Kommentar