You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When allowing tenant to supply their own DB name and external connection we are exposed to different object naming conventions for example, database 2020conjuror role 2020conjur_role
When the object starts with integer, Conjur fails to convert it to String - leading us to errors like so when loading policy (we create temp schema for each load policy):
The error source can be found here orchestrate.rb and here schemata.rb, however it is not limited to those references and can occur in different flows, we should escape and convert each database object (db name, role name & schema name etc.) to Strings
Steps to Reproduce
Steps to reproduce the behavior:
Create DB/Schema/Role starting with integer
Supply it into Conjur by external DB url and not proprietary DB usage flow
Run load policy
Expected Results
200 OK and loaded policy
Actual Results (including error logs, if applicable)
500 Server error with stack trace above
Reproducible
Always
Sometimes
Non-Reproducible
Version/Tag number
all
Environment setup
External DB setup, helm/docker-copmose
Additional Information
None
The text was updated successfully, but these errors were encountered:
Summary
When allowing tenant to supply their own DB name and external connection we are exposed to different object naming conventions for example, database
2020conjur
or role2020conjur_role
When the object starts with integer, Conjur fails to convert it to String - leading us to errors like so when loading policy (we create temp schema for each load policy):
The error source can be found here orchestrate.rb and here schemata.rb, however it is not limited to those references and can occur in different flows, we should escape and convert each database object (db name, role name & schema name etc.) to Strings
Steps to Reproduce
Steps to reproduce the behavior:
Expected Results
200 OK and loaded policy
Actual Results (including error logs, if applicable)
500 Server error with stack trace above
Reproducible
Version/Tag number
all
Environment setup
External DB setup, helm/docker-copmose
Additional Information
None
The text was updated successfully, but these errors were encountered: