Identitysettings reference case sensitive for Linux
See original GitHub issueBug description
IdentitySettings reference will fail because it’s referenced as identitySettings (lowercase i). Casing differences are problematic on Linux machines, but not an issue on Windows machines.
Renaming this file to identitySettings.ts
solves it.
Reproduction steps
- Run
npm run publish
on a linux machine on the self-hosted portal.
Is your portal managed or self-hosted?
self-hosted
Release tag or commit SHA (if using self-hosted version)
2.12.0
Issue Analytics
- State:
- Created 2 years ago
- Comments:6
Top Results From Across the Web
Configuring Directory Server for case-sensitive user ID ... - IBM
Answer. You can change the schema to have case sensitive user login names. The Security (or Tivoli) Directory Server schema can be changed ......
Read more >Linux Both Case Sensitive AND Case Insensitive and Always ...
Ubuntu is not partially case sensitive. It's always case sensitive. filename.txt and Filename.txt are two different files and can be placed in the...
Read more >Is the username in Unix case sensitive?
Hostnames and domain names are clearly case insensitive by the DNS standard (see RFC4343). Usernames stored on a local backend (/etc/passwd) or ...
Read more >Case-sensitivity - HCL Product Documentation
Linux, the UNIX system, and Windows® observe different conventions for case-sensitivity in file name lookup: Linux and the UNIX system are case sensitive; ......
Read more >Configuration Settings that Must Use the Same Values
http: is case-sensitive. Therefore, the case of all SP ID- and IdP ID-related settings must match.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
In another branch. But let me just cherry-pick it right now: #1583
Fixed in scope of another issue.