App Builder: Authentication for apps
Why App Builder authentication matters
Authentication is a crucial aspect of securing your app and ensuring that only authorized users can access its content. When users attempt to view live pages within your app, authentication is required. We've extended our existing authentication system to App Builder, leveraging Entra ID and Google authentication, just like the rest of Rewst. This ensures a consistent and secure user experience across the platform.
How authentication works
When a user tries to access live pages within your app, they will be redirected to the login page.
Users have the option to authenticate using Entra ID or Google credentials. This provides a seamless and familiar login experience.
Once authenticated, the system performs an authorization check to ensure the user has the necessary permissions to view the requested content.
If the authentication and authorization checks pass, the user is granted access to the live pages.
Default login page
Upon creating your app, you'll notice that a login page is automatically included as one of the default pages. This login page is a fundamental part of ensuring that users authenticate themselves before accessing any live content within your app.

You have the flexibility to customize the login page according to your app's branding and design, creating a cohesive and personalized experience for the users who log into your app. For more on editing pages, see our pages documentation here.
Configure a webhook trigger for CORS requests
When referencing a Rewst web hook in JavaScript in an app builder page(or outside of Rewst), you may see the error TypeError: Failed to fetch. This is due to blocking by your browser. See our documentation for how to set up this particular type of trigger here. 
Last updated
Was this helpful?

