Subiendo y probando nuestra política personalizada

How to upload files to the Azure portal correctly?

For any developer looking to integrate identity solutions into Azure, understanding how to upload files correctly is essential. This process encompasses uploading XML files with a specific hierarchy to avoid errors and ensure all applications run smoothly.

What is the correct order to upload files?

Correct file uploading involves following an established hierarchy:

1. Trons framework base: This is the file that should be uploaded first, as it is the fundamental base.
2. Trons framework extensions: This file is used next and depends on the base.
3. Sign up or signIn: This file handles authentication and should be uploaded after the extensions.
4. Password reset or profile edit: These are uploaded according to the specific needs of the project.

Using this sequence helps to avoid errors related to missing framework extensions, which is crucial for successful development.

How are custom policies tested?

To verify that the policies were loaded and configured correctly, test applications are used. In this case, the demoApp sample application is used.

1. Once it is run, you will be able to see if the authentication is successful.
2. The results are redirected to JWT.ms where it is possible to see the issued tokens.

It is worth remembering that at this stage, no concessions with different scopes are made yet, therefore, only ID tokens are accessed.

How to leverage login with Facebook and other networks?

Azure allows you to extend authentication to include social networking platforms, such as Facebook. To do this:

• Refer to the Facebook Developers documentation to register an application ID and application secret.
• Configure this information in Azure system policies and keys.

This integration can be extended to other social networks, making it easier for users to access from popular platforms and improving the user experience.

How to create and register new users?

The process of creating new users is critical to managing identities in Azure. The use of temporary emails is a viable option for testing:

1. Temporary Email: Services such as TMail are used to receive notifications that are sent by Azure Active Directory B2C.
2. Verification code: Use the code received by mail to verify your identity.
3. Secure password: Create a password that meets the requirements of the established regular expression (8-16 characters, including at least three uppercase, lowercase, digits or special characters).
4. User information: Provide a display name, which will be visible on the system.

After completing these steps, the new user is registered and visible in the user directory, where his or her unique Object ID can be verified, ensuring authenticity and traceability.

These practices and structures ensure efficient handling of identity solutions, promote security and facilitate user management within the Azure ecosystem.