cancel
Showing results for 
Search instead for 
Did you mean: 

Problems with Logon screen

Former Member
0 Kudos
115

We are in a CLM wave 9 Implementation project and we’re facing an issue when login to “fsbuyer”

We access the following URL http://<customer server>:50000/sourcing/fsbuyer/portal/login and access the standard login page:

In the standard login page, we complete user and pass and the system rise the following error

This behavior occurs randomly and after few attempts, we can login with the same user and pass that we couldn’t before. This occurs for every created user.

Find bellow our Directory configuration.

Any clue about this issue?


Regards,

Martin

Accepted Solutions (1)

Accepted Solutions (1)

former_member89217
Contributor
0 Kudos

Hi Martin,

I notice you are using the local driver for your users. Keep in mind this is not a supported configuration for a production environment.  Do you have multiple instances (server nodes etc)? If yes this absolutely will not work with local authenticator. This is a file based user store and only works properly with a single instance.  Next observation is the directory is tied to the system default cluster. This is not typical.  There should be an additional cluster configuration for the enterprise. This cluster would have an explicit hostname and the directory configurations would be tied to this cluster. The default cluster is used for the system user.

Regards,

Gary

Former Member
0 Kudos

Hello Gary,

thanks a lot for your response.

Below you can see our default cluster configuration. We have modified it in order to link this cluster with enterprise context but the issue persist.

Do you think that maybe it might be related to a installation / basis issue ?

Thanks in advance,

regards.

Martin

former_member89217
Contributor
0 Kudos

This is still not an appropriate configuration. You should have a sepearte cluster for the enterprise. And secondly local authentication will not work reliable with more than 1 service.  Each service would have a password file and neither would be complete.

Regards,

Gary

Former Member
0 Kudos

Thanks Gary!
We have changed the cluster configuration and now it's working properly.

Best regards,

Martin

former_member89217
Contributor
0 Kudos

glad to help.

Gary

0 Kudos

Hi Gary,

As per your reply, we need to have the following configuration in CLM server.

*) One Context: System Context or other name.

*) Two Cluster Configurations:

- System Default Cluster: used by the system user to login (System Default Cluster must be checked).

- Enterprise Cluster: used by all the buyer users (System Default Cluster must be unchecked).

If we use Local Directory, the related cluster (Enterprise Cluster) must have only one Cluster Member. As you saw, we have two cluster members. Implications if we delete one Cluster Member at this time?

Thanks again

Best Regards

Ale

Answers (0)