It is strongly recommended for security concerns, that in the production environment, you shall safeguard the server resources through implementing an authentication server with PowerServer.
If you have selected an auth template (built-in JWT server, built-in OAuth server, built-in AWS Cognito server, Azure Active Directory service etc.) in the project settings, make sure to follow the relevant instructions to modify the PowerBuilder client app and re-deploy the PowerServer project. If you have selected to use built-in AWS Cognito server, you also need to make changes to the deployed authentication template.
-
Use built-in JWT server: Includes a built-in authentication server that supports JWT or bearer tokens. See Tutorial 6: Authenticating your apps > Using JWT for more information.
-
Use built-in OAuth server: Includes a built-in authentication server based on IdentityServer4 framework that works with the OAuth 2.0 authorization flows. See Tutorial 6: Authenticating your apps > Using OAuth 2.0 for more information.
-
Use built-in AWS Cognito server: Includes a built-in authentication server that works with the Amazon Cognito user pool. See Tutorial 6: Authenticating your apps > Using Amazon Cognito for more information.
-
Use external Azure Active Directory service: Includes templates that work with Azure AD or Azure AD B2C. See Tutorial 6: Authenticating your apps > Using Azure Active Directory for more information.
If you have selected "Use external auth service" in the project settings, see Tutorial 6: Authenticating your apps > Using other auth servers for more information on how to incorporate the other auth servers that work with the OAuth flows or JWT, such as Okta OIDC (OpenID Connect).
