June 2024 Summaries

Spring Boot, a framework for creating stand-alone, production-grade applications, is often used in combination with a separate frontend framework like React. This setup benefits from the use of Spring Security to handle authentication and authorization, especially in multi-tenant environments where roles and permissions are critical. A common configuration involves using Spring Boot as the backend with an external authentication service, like PropelAuth, which simplifies the authentication process by handling it outside of the backend. The backend must validate authentication information and ensure users have the necessary permissions to make requests, often using JWTs for token validation. PropelAuth supports B2B and multi-tenant setups by providing features like organizations, role-based access control, and enterprise SSO, allowing users to belong to multiple organizations with specific roles. The backend can restrict access to routes based on users' roles and permissions using an AuthorizationManager, which checks if users have the correct roles and permissions within their organization. This setup also accommodates dynamic authorization changes based on factors like payment plans, utilizing PropelAuth's Role Mappings to adjust permissions without altering the code.

Recent updates have introduced several new features and enhancements, including a new option to log in with Apple, official support for the Spring Boot framework, and improved user management capabilities allowing the viewing and handling of pending organization invites through the dashboard. The interface now offers an option to hide the project name on signup/login pages, and a new user property type, 'Phone Number,' has been added alongside a new organization field, 'legacy_org_id,' which aids in migration from external systems. Additionally, wildcards can be used in OAuth redirect URLs, email confirmations can be disabled for SSO/SAML connections, a new webhook notifies when users are invited to organizations, and an API call can log users out of all sessions. Documentation has been restructured for improved accessibility.

PropelAuth has enhanced its Role-Based Access Control (RBAC) system by introducing Roles & Permission Mappings, allowing for configuration of roles and permissions on a per-organization basis without requiring code changes. This is exemplified by the ability to create separate mappings for different pricing plans, such as enabling a Data Export feature exclusively for paid users and automatically switching them over to the Paid mapping via the PropelAuth dashboard or programmatically. The update, aimed initially at pricing plan differentiation, offers broader applications, reflecting its flexibility and adaptability. Additionally, the release includes various updates such as eliminating the requirement for SAML logins for users with internal roles, the use of login_hint during SAML logins to streamline user access, supporting Atlassian as a new SSO option, the ability to disable roles, new APIs for resending confirmation emails, and the capability to invite users to organizations directly through the dashboard.