Prevent or stop credential cache in openHistorian 2.6.x

GPA Products openHistorian
1

Hi Ritchie,

Currently, I’m using openHistorian 2.6.30.x.
Is there any option to stop or prevent credential cache?

Thanks & Regards
Logu

2

Might be as simple as commenting out a line of code or two - but I don’t think there’s an option to disable this feature.

Thanks,
Ritchie

3

Hi Ritchie,

Good Morning.

Could you please locate the code, where we need to comment? So that I will try.
Also in 2.8, do we have any switch/option to handle this.
Reason is whenever credential cache file is reaching size “7 KB”, not allowing to login and saying like “Attempting authentication”.

Regards
Logu

4

After a code review, it could be that the system is trying to compact the file and causing some delays.

Are you using most database or Active Directory / local machine based authentications?

Thanks,
Ritchie

5

FYI - updated 2.8 code base to include option to disable:

6

Hi Ritchie,

From my analysis, actual cause:

When using both database user as well as Active Directory users.

For internal users, we have provided active Directory users and external users, we provided database user. When login to openHistorian 2.6 portal using both users at the time, we are getting this error.

Also, I found one more scenario.

  1. We have below type of usernames
    a. Local database username: logu
    b. Active Directory username: domain\logu

  2. When login using database username “logu”, its always giving 401 error.

Thanks & Regards
Logu

7

Hi Ritchie,
If I incorporate this code alone, will it solve problem or do we need to add or check other modules as well?

8

This code update will allow disabling of the credential cache, which you had identified as the problem spot.

I do not believe this will help with the case where you have both a database user and a domain user with the same name, at this point, this will likely default to AD user and/or have unexpected results.

Thanks,
Ritchie