Hi:
I'm very new to Apex Oracle. My current goal is to allow user access in such a way that associated user information (job title, etc.) can also be used in the database. If I understand correctly, I should be setting up custom authentication that will allow user information to be stored in a table rather than use Apex Oracle Accounts or Social or some other authentication scheme. If I'm not on the right track, the rest of this question probably doesn't matter and I should do something different. Let me know if I'm way off in this first paragraph.
I think I'm almost there with this process. I've got my table set with user_id, email, password, and salt and other identifiers that I will use elsewhere, such as name, location, etc.
At this point, I want to ensure the password field contains only hashed information, so I have a package set up that will do that as the password is stored, but I'm running into problems. So far I don't think it is anything to do with my code. Even simple SQL test statements fail.
The compiler complains to me that PLS-00201: identifier 'SYS.DBMS_CRYPTO' must be declared.
Multiple references and AI suggestions tell me I need to GRANT EXECUTE ON DBMS_CRYPTO TO your_schema_name or TO your_user_name. I have yet to make this line work. Or else SYS.DBMS_CRYPTO…
The first troubleshooting step usually described is to ensure that you have SYS privileges. I'm the only user on the workspace, so I'm not sure what else I could be.
I'm also happy to use another method to secure passwords as long as it remains with up to date security as can best be achieved in Apex and I can also continue with goals in paragraph #1. In fact, I'd be much happier with authentication methods that don't require me to write them or maintain them, but seems like this is the necessary path to take.
Thanks,
strider841