Loading
Office 365 Cloud connector configuration
Hello my dears. I've created a local SLM-User with the API role for configure the Office 365 connector. But if I insert the server and the credentials, I get a error message (see attachement). I've played arround with the full server name and shorter/simplier passwords, but without success. Any suggestions how to fix this or whats the reason? Kind regards Kai

  • Geoffrey Macquet (Flexera Software)

    Hi ‌, by checking our Knowledge Base i found the following information: Just to be sure that every setting is correct, could you please check a few things: Check the settings for the APIuser in the SMACC and it has the role of "API Users" Are you able to access the Web Gui with the same credentials. Verify that â—¦ Microsoft Online Services Sign-In Assistant (64-bit version)  & Windows Azure Active Directory Module for Windows PowerShell (64-bit version) were installed. Check if Windows Authentication is enabled for the Snow License Manager site. If true, an exception has to be made for the API in the SLM web configuration.   Add the following changes in the <configuration> section of the web.config file: <location path="api">    <system.webServer>       <security>          <authentication>             <anonymousAuthentication enabled="true" />             <basicAuthentication enabled="false" />             <windowsAuthentication enabled="false" />           </authentication>       </security>    </system.webServer> </location> This area is located near the bottom half of the web.config file: You might need to reset the IIS (open administrative CMD and type in "iisreset") to apply the changes. If this does not help i strongly recommend to revert the changes and contact Snow Support. Let me know if this helps! Best Regards Geoffrey Macquet   Customer Success Manager EMEA
    Expand Post
    • Hello Geoffrey, many thanks for your quick answer. the user has the "API User" role Ah, okay, that can be the reason, I can't open http://localhost/api - I got the "404 - File directory not found" error message. But I'm a little bit surprised then I've configured this last year for my collegue how wants to access from Jira into the SLM. And last year it has been working. And I got no information that this does not work anymore. Yes, Microsoft Online Services Sign-In Assistant (64-bit version)  & Windows Azure Active Directory Module for Windows PowerShell (64-bit version) are installed yesterday by myself the configuration at the web.config file I've done last year (because of Jira). I've just checked again and that is set as desired. What could be the reason for the problem with the API call at http://[SLM-Servername]/api Or its better to rise a support ticket? Kind regards Kai
      Expand Post
      • Geoffrey Macquet (Flexera Software)

        Hi ‌, As this is mostly due to some configuration which needs to be checked, i think it would be best to create a support ticket, as i'm out of ideas. Please link this thread to the ticket so that the support engineer can also see the first troubleshooting steps you took. Best Regards Geoffrey Macquet Customer Success Manager EMEA
        Expand Post
        • Hello Geoffrey, with a fresh view on this issue this morning, I found the solution and it's my mistake. I had taken the settings from the manual, but we changed the default port. As so often, the problem sits in front of the monitor. Thanks a lot and kind regards Kai
          • Geoffrey Macquet (Flexera Software)

            Good morning ‌, Thank you for sharing the solution, happy to hear Well that might have been a simple question regarding the default port, did not took this into consideration! All the best, Geoffrey Macquet Customer Success Manager EMEA
            Expand Post
          • Geoffrey Macquet (Flexera Software)

            Good morning ‌, Thank you for sharing the solution, happy to hear Well that might have been a simple question regarding the default port, did not took this into consideration! All the best, Geoffrey Macquet Customer Success Manager EMEA
            Expand Post

Loading
Office 365 Cloud connector configuration