3 May: DB User access for every project
With this update Uncodie can share the API access for your project and a more powerful control in your project data base.
Improved 💪🏼
Enhanced Database Security and Personalization.
To leverage new security features, legacy projects must undergo recompilation and publication. This update introduces a significant enhancement in database management practices. Specifically, we have shifted to using unique usernames and passwords for database access, tailored to each project's needs. This approach not only heightens the overall security of our Platform as a Service (PAAS) but also allows for more personalized usage of PostgreSQL databases. With this change, project teams can safely share their database credentials while maintaining strict access control to their assigned databases.
Fixing 🔧
Troubles with no-code query compilation.
To address the issue, we implemented a regular expression designed to eliminate spaces. This solution became necessary when we discovered that the element in question contained a space in its name.
The addition or removal of environment variables was not visible.
The solution involved reconfiguring the section to leverage Uncodie's latest features, which support the intended behavior. Despite adjusting variables in the Backoffice App, no interaction cues appeared, mistakenly implying malfunction.
Access is denied when creating a new project.
Solution for Access Denied Error on New Project Creation
When a new project is created in the app, users may encounter an "access denied" error when trying to access it. This issue arises because the validation process fails to recognize the new project immediately upon creation.
Proposed Solution: To resolve this issue, implement an automatic refresh of the user's project information as soon as a new project is created. This ensures the validation process includes the newly created project, thereby eliminating the "access denied" error.
Last updated
Was this helpful?