WQMan

joined 1 week ago
sorted by: new top controversial old
Reevaluating my password management in c/[email protected]
[โ€“] [email protected] 2 points 2 days ago* (last edited 2 days ago) (1 children)

+1 to this; Time spent on your setup is an important factor too.

The more important your data is, the more time you are going to need to spend maintaining your system to ensure security, backups and fail-overs. Not everyone has luxurious amount of time to spend on their home-lab everyday.

Reevaluating my password management in c/[email protected]
[โ€“] [email protected] 5 points 2 days ago (4 children)

Well, not wrong that it solves the problem, but with data breaches happening frequently, I wouldn't want to repeat 1 single password for all services lol.

Even if companies hash passwords, it's still a gamble whether they are using an up-to-date hash algorithm (or if they do even hash it, lol). Plus, generally best to avoid exposing passwords, hashed or not, in the first place.

28
Recommendations for External GPU Docks for Home Lab Use - Lemmy (lemmy.ml)
4
OpenText - Allow case-insensitive with AWS RDS PostgreSQL (lemmy.ml)
submitted 6 days ago* (last edited 6 days ago) by [email protected] to c/[email protected]
0 comments fedilink
 

Hi all, hopefully this question isn't out of context.

I'm currently working with OpenText Content Management Solution hosted on AWS using Kubernetes.

Currently facing a challenge related to case sensitivity in our PostgreSQL database.

We are using AWS RDS PostgreSQL v15.0 with OpenText version 24.4.6.

By default, PostgreSQL is case-sensitive, which is causing issues with the content management services; Users are looking for case-insensitive functionality, but our current setup does not support this.

Did want to suggest switching to Oracle Database or Microsoft SQL, as both can be configured for case insensitivity. Unfortunately, due to organization requirements, I cant change it.

I have a friend who also used OpenText Content Services, but he didn't encounter the same issue because he was using Microsoft SQL. Additionally, he was running it on a bare metal Windows server rather than Kubernetes.

I looked through the official Cloud Deployment Guide for OpenText, but I couldn't find any configuration options related to case insensitivity.

Additionally, I explored suggested solutions on StackOverflow regarding case-insensitive queries or collation, but these are not applicable since we do not have control over the SQL queries or table creation in OpenText.

Currently the organization is trying to get developers to customize it on the API level to make it case-insensitive. But was wondering if anyone encountered a similar issue and managed to configure OpenText to be case-insensitive instead.