• State Verified Answer
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 47 subscribers
  • Views 4941 views
  • Users 0 members are here
Options
Related

authenticate to SDL KC 12

tintinno tintinno

I tried connecting to an SDL Knowledge Center 12 instance with the command:

$ishSession = New-IshSession -IshPassword $password -IshUserName $username -WsBaseUrl $url

I got this error:

New-IshSession : WSTrust endpoint not configured: '/InfoShareSTS/issue/wstrust/mixed/username/'

A Fiddler capture of logging in through the web interface shows a POST to /InfoShareSTS/account/signin with the request body:

UserName=firstName+lastName&Password=myPassword&EnableSSO=false

Is this an abnormal authentication setup or can ISHRemote's New-IshSession command replicate this?
Rate translation
×
Suggest better translation
×
Parents
  • 0
    Hi Tintinno

    ISHRemote can handle username/password authentication towards the built-in InfoShareSTS/ISHSTS.

    As you rightfully hide the urls (like $url) I can only tell you what the code is looking for. The error is thrown on line 834 on github.com/.../InfoShareWcfConnection.cs

    My generic guess would be that the web services url you enter for a client tool like Publication Manager, should be passed in your $url. That should be enough. Make sure it holds an s near httpS://.

    -Dave
  • 0 in reply to Dave De Meyer

    Hi Dave!

    I verified the protocol was https and the endpoint '/InfoShareWS/' matched the service URL in Publication Manager. I'm attaching another attempt with the -Verbose and -Debug flags (with domains changed to 'example.com' etc.). Please let me know if anything stands out. Thanks!

     

    New-IshSession -IshUserName $username -IshPassword $password -WsBaseUrl 'example.com/.../' -Verbose -Debug

    DEBUG: NewIshSession 20180926.101644.761 BeginProcessing
    VERBOSE: NewIshSession Connecting to WsBaseUrl[https://example.com/InfoShareWS/] IshUserName[Username] IshPassword[**********************]
    DEBUG: NewIshSession 20180926.101649.022 Connecting to WsBaseUrl[https://example.com/InfoShareWS/] IshUserName[Username] IshPassword[**********************] Timeout[00:00:20] Time
    outIssue[10675199.02:48:05.4775807] TimeoutService[10675199.02:48:05.4775807] IgnoreSslPolicyErrors[False]
    DEBUG: NewIshSession 20180926.101649.023 Enabling Tls, Tls11 and Tls12 security protocols
    DEBUG: NewIshSession 20180926.101649.032 Incomming infoShareWSBaseUri[https://example.com/InfoShareWS/]
    DEBUG: NewIshSession 20180926.101649.035 LoadConnectionConfiguration uri[https://example.com/InfoShareWS/connectionconfiguration.xml] timeout[00:00:20]
    DEBUG: NewIshSession 20180926.101649.273 InitializeInfoShareWSBaseUri uri[https://example.com/InfoShareWS/]
    DEBUG: NewIshSession 20180926.101649.274 Normalized infoShareWSBaseUri[https://example.com/InfoShareWS/]
    DEBUG: NewIshSession 20180926.101649.275 Resolving endpoints
    DEBUG: NewIshSession 20180926.101649.277 GetWsdlImporter wsdlUri[https://example.com/InfoShareWS/Wcf/API25/Application.svc?wsdl]
    DEBUG: NewIshSession 20180926.101650.030 ApplyQuotas on serviceEndpoint[https://example.com/InfoShareWS/Wcf/API25/Application.svc]
    DEBUG: NewIshSession 20180926.101650.037 Resolved endpoints
    DEBUG: NewIshSession 20180926.101650.038 CreateConnection _serverVersion GetApplication25Channel
    DEBUG: NewIshSession 20180926.101650.040 Issue Token
    DEBUG: NewIshSession 20180926.101650.041 FindIssuerEndpoint
    DEBUG: NewIshSession 20180926.101650.042 FindIssuerEndpoint issuerMetadataAddress[https://example.com/InfoShareSTS/issue/wstrust/mex/] issuerAddress[https://example.com/InfoShareSTS/issue/wstrust/mixed/username]
    DEBUG: NewIshSession 20180926.101650.043 GetWsdlImporter wsdlUri[https://example.com/InfoShareSTS/issue/wstrust/mex/]
    DEBUG: NewIshSession 20180926.101650.115 GetWsdlImporter wsdlUri[https://example.com/InfoShareSTS/issue/wstrust?wsdl/]
    VERBOSE: NewIshSession Connecting to IssuerWSTrustUrl[https://example.com/InfoShareSTS/issue/wstrust/mixed/username/]
    DEBUG: NewIshSession 20180926.101650.194 InitializeIssuerWSTrustEndpointUri uri[https://example.com/InfoShareSTS/issue/wstrust/mixed/username/]
    DEBUG: NewIshSession 20180926.101650.196 FindIssuerEndpoint issuerWSTrustEndpointAbsolutePath[/InfoShareSTS/issue/wstrust/mixed/username/]
    New-IshSession : WSTrust endpoint not configured: '/InfoShareSTS/issue/wstrust/mixed/username/'.
    At line:1 char:1
    + New-IshSession -IshUserName 'Username' -IshPassword '************ ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     + CategoryInfo : NotSpecified: (:) [New-IshSession], InvalidOperationException
     + FullyQualifiedErrorId : NewIshSession,Trisoft.ISHRemote.Cmdlets.Session.NewIshSession
Reply
  • 0 in reply to Dave De Meyer

    Hi Dave!

    I verified the protocol was https and the endpoint '/InfoShareWS/' matched the service URL in Publication Manager. I'm attaching another attempt with the -Verbose and -Debug flags (with domains changed to 'example.com' etc.). Please let me know if anything stands out. Thanks!

     

    New-IshSession -IshUserName $username -IshPassword $password -WsBaseUrl 'example.com/.../' -Verbose -Debug

    DEBUG: NewIshSession 20180926.101644.761 BeginProcessing
    VERBOSE: NewIshSession Connecting to WsBaseUrl[https://example.com/InfoShareWS/] IshUserName[Username] IshPassword[**********************]
    DEBUG: NewIshSession 20180926.101649.022 Connecting to WsBaseUrl[https://example.com/InfoShareWS/] IshUserName[Username] IshPassword[**********************] Timeout[00:00:20] Time
    outIssue[10675199.02:48:05.4775807] TimeoutService[10675199.02:48:05.4775807] IgnoreSslPolicyErrors[False]
    DEBUG: NewIshSession 20180926.101649.023 Enabling Tls, Tls11 and Tls12 security protocols
    DEBUG: NewIshSession 20180926.101649.032 Incomming infoShareWSBaseUri[https://example.com/InfoShareWS/]
    DEBUG: NewIshSession 20180926.101649.035 LoadConnectionConfiguration uri[https://example.com/InfoShareWS/connectionconfiguration.xml] timeout[00:00:20]
    DEBUG: NewIshSession 20180926.101649.273 InitializeInfoShareWSBaseUri uri[https://example.com/InfoShareWS/]
    DEBUG: NewIshSession 20180926.101649.274 Normalized infoShareWSBaseUri[https://example.com/InfoShareWS/]
    DEBUG: NewIshSession 20180926.101649.275 Resolving endpoints
    DEBUG: NewIshSession 20180926.101649.277 GetWsdlImporter wsdlUri[https://example.com/InfoShareWS/Wcf/API25/Application.svc?wsdl]
    DEBUG: NewIshSession 20180926.101650.030 ApplyQuotas on serviceEndpoint[https://example.com/InfoShareWS/Wcf/API25/Application.svc]
    DEBUG: NewIshSession 20180926.101650.037 Resolved endpoints
    DEBUG: NewIshSession 20180926.101650.038 CreateConnection _serverVersion GetApplication25Channel
    DEBUG: NewIshSession 20180926.101650.040 Issue Token
    DEBUG: NewIshSession 20180926.101650.041 FindIssuerEndpoint
    DEBUG: NewIshSession 20180926.101650.042 FindIssuerEndpoint issuerMetadataAddress[https://example.com/InfoShareSTS/issue/wstrust/mex/] issuerAddress[https://example.com/InfoShareSTS/issue/wstrust/mixed/username]
    DEBUG: NewIshSession 20180926.101650.043 GetWsdlImporter wsdlUri[https://example.com/InfoShareSTS/issue/wstrust/mex/]
    DEBUG: NewIshSession 20180926.101650.115 GetWsdlImporter wsdlUri[https://example.com/InfoShareSTS/issue/wstrust?wsdl/]
    VERBOSE: NewIshSession Connecting to IssuerWSTrustUrl[https://example.com/InfoShareSTS/issue/wstrust/mixed/username/]
    DEBUG: NewIshSession 20180926.101650.194 InitializeIssuerWSTrustEndpointUri uri[https://example.com/InfoShareSTS/issue/wstrust/mixed/username/]
    DEBUG: NewIshSession 20180926.101650.196 FindIssuerEndpoint issuerWSTrustEndpointAbsolutePath[/InfoShareSTS/issue/wstrust/mixed/username/]
    New-IshSession : WSTrust endpoint not configured: '/InfoShareSTS/issue/wstrust/mixed/username/'.
    At line:1 char:1
    + New-IshSession -IshUserName 'Username' -IshPassword '************ ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     + CategoryInfo : NotSpecified: (:) [New-IshSession], InvalidOperationException
     + FullyQualifiedErrorId : NewIshSession,Trisoft.ISHRemote.Cmdlets.Session.NewIshSession
Children
  • 0 in reply to tintinno tintinno

    I compared this to another debug log, and I noticed that in a few places a final slash is present in this log but missing in the log of the system I can connect to.

    1. GetWsdlImporter wsdlUri[https://example.com/InfoShareSTS/issue/mex/]
    2. GetWsdlImporter wsdlUri[https://example.com/InfoShareSTS/issue/wstrust?wsdl/]
    3. VERBOSE: NewIshSession Connecting to IssuerWSTrustUrl[https://example.com/InfoShareSTS/issue/wstrust/mixed/username/]

    I can retrieve both connectionconfiguration.xml files and see that the URL ends with "username" in the 2014 instance and "username/" in the 2016 instance. So perhaps the problem is only with "mex/" and "wstrust?wsdl/". GET requests to the 2016 instance return the XML <wsdl:definitions> etc only if wstrust?wsdl is missing the final slash. 

    Since I can't fix this server-side, is it possible to update the ISHRemote client to trim the final slash if it exists? I'm not that familiar with C#, and I don't have a system setup for testing these changes, but perhaps something like this:

     950 private WsdlImporter GetWsdlImporter(Uri wsdlUri)
     951 {
     952     if ( wsdlUri.EndsWith("/") )
     953     {
     954         wsdlUri = wsdlUri.TrimEnd("/"); 
     955         _logger.WriteDebug($"Trimming final slash from wsdlUri");
     956     }
     957     _logger.WriteDebug($"GetWsdlImporter wsdlUri[{wsdlUri}]");

    Then the final slash won't be on the /mex ending either, so the issuerMetadataAddress.Uri.AbsoluteUri.Replace("/mex", "?wsdl") statement on line 823 won't leave behind a trailing slash.