Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Suggested Answer
  • Replies replies
    3
  • Answers answer
    1
  • Subscribers subscribers
    22
  • Views views
    367
  • Users 0 members are here
Related
Options

Can not log in through the WebClient

Subha Gangopadhyay

Hi Folks,

I have an installation setup where my Workgroup Server and my WebClient (& ServiceAPI) are hosted in two different servers. The same domain account has been used to do the installation. 

Initially I was facing issues in launching the WebClient. But after enabling the Anonymous Authentication in the IIS for the WebClient package, I am able to launch the WebClient UI. But I am not able to login as I am getting the error message that 'Content Manager web client is unable to establish a connection  to the Web service' (screen shot given below).

Initially, I was facing error in launching ServiceAP(localhost:80/.../index) also. But it got resolved after adding my domain account as 'Trusted server account' for my dataset in the Content Manager Enterprise Studio (though the documentation suggests that it is not needed as I am using same domain account for the two installation).

Any help will be much appreciated. 

 

Parents
  • 0  

    Hi  
    Can you confirm which version of CM you are trying to install ? 
    For 9.4 onwards you must have the workgroup server application installed on the same server that hosts the web client/service API.
    Typically you would use Windows Authentication for the Web client instead of Anonymous, setting the related Application Pool user to the service account used to run CM.

    Can you give some clarification on the CM version and provide details of the hptrim.config ( ServiceAPI) and hprmServiceAPI.config (web client) , obfuscating the server details where relevant. You may have used localhost as the information for the WorkGroupServer URL, instead of the actual WorkGroup server. Providing this information will assist in diagnosing. 

Reply
  • 0  

    Hi  
    Can you confirm which version of CM you are trying to install ? 
    For 9.4 onwards you must have the workgroup server application installed on the same server that hosts the web client/service API.
    Typically you would use Windows Authentication for the Web client instead of Anonymous, setting the related Application Pool user to the service account used to run CM.

    Can you give some clarification on the CM version and provide details of the hptrim.config ( ServiceAPI) and hprmServiceAPI.config (web client) , obfuscating the server details where relevant. You may have used localhost as the information for the WorkGroupServer URL, instead of the actual WorkGroup server. Providing this information will assist in diagnosing. 

Children

  • Suggested Answer

    0 in reply to   

    Hi Martin,

    Thank you for your assistance. You were correct; the issue was related to Anonymous Authentication. Our organization’s policy does not permit Windows Authentication by default. However, after installing Windows Authentication through IIS roles, I was able to log in successfully.

    For your reference, I am using Content Manager 24.3 and configured the server hostname as the primary Workgroup server name during the Web Client installation.

    Currently, I am having difficulty locating the Log Out button in the Web Client. Additionally, our requirement is to support both Basic and SSO-Based Authentication within the application. I am unable to create a user (Location) with a username and password based login mechanism. Could you please suggest me about how to configure Basic Authentication in Content Manager application?

    Thank you for your help.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.