My post said nothing about storing "raw passwords in a database." Therefore, it is unclear what you're replying to.
I am talking about Oracle Database Users and Oracle Database's password limitations therein. The reason for Oracle Database's password restrictions isn't to do with how they're stored on disk (which is secure as if 12c[0]), it is to do with how they were implemented originally (i.e. passwords are implemented as database objects, and database objects have max lengths and other naming rules which apply to passwords).
Most likely what's being talked about here is using Oracle to track identity across accesses to data on a per user basis, for permissions and auditing, and that piggybacking on Oracle's own password management with its own restrictions.
Comments
If you're storing a raw password in a database, limiting specific characters is waaaay down on the list of things you're doing wrong.
My post said nothing about storing "raw passwords in a database." Therefore, it is unclear what you're replying to.
I am talking about Oracle Database Users and Oracle Database's password limitations therein. The reason for Oracle Database's password restrictions isn't to do with how they're stored on disk (which is secure as if 12c[0]), it is to do with how they were implemented originally (i.e. passwords are implemented as database objects, and database objects have max lengths and other naming rules which apply to passwords).
[0] https://seanstuber.com/how-oracle-stores-passwords/
Most likely what's being talked about here is using Oracle to track identity across accesses to data on a per user basis, for permissions and auditing, and that piggybacking on Oracle's own password management with its own restrictions.