Hi Subha Gangopadhyay 
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. 

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.

Hi Subha,

The Log Out button is not present with a Windows Authentication method, this is as most browsers can be configured to 'auto-pick-up' your credentials for the currently logged in user. If you were presented with a Log In box, then try clearing your browser cookies / history to then log in with a different set of credentials.

To support both Basic and SSO, it's recommended to have 2x sites, as a single CM web-client instance doesn't work great with both at the same time. This is as Basic Auth is handled by IIS, where SSO is handled by the Application and requires IIS Auth to be set to Anonymous.

You can do this by having another copy of the site deployed on a different server, or on the same server (with different bindings to allow each of the sites to be accessed).

Basic Authentication can be configured by enabling it within IIS against the website.

To configure SSO you can do so by following this guide:

https://content-manager-sdk.github.io/Community/233/oidc.html#oidc_azuread

It sounds like you may benefit from more direct engagement with an implementation partner. I recommend reaching out to your preferred Content Manager provider for some more detailed guidance.

-Scotty