You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Overview:
Authentication is a critical component of the test automation process. The sample script employs browser-based authentication, which offers a range of options to authenticate with Microsoft Entra. This method generates a persistent browser cookie, allowing for non-interactive execution of subsequent tests. The management of these browser cookies is governed by the guidelines provided in the Microsoft Entra documentation on session lifetime and conditional access policies.
Details:
As the Power CAT Engineering team looked at the different authentication options for the CoE Starter Kit, we started with browser-based authentication for local testing. This approach works with the conditional access policies of our environments and allows a quick and less intrusive process to authenticate as different test personas.
As we look at our continuous integration and deployment process, we will evaluate certificate-based authentication to determine the correct mix of authentication and management trade-offs to select authentication options and what secret store is used to securely host the login credentials.
Key Questions
What are the key challenges you have faced with browser-based authentication in your test automation processes?
Have you implemented certificate-based authentication in your test automation? If so, what were the trade-offs and benefits?
What compliance challenges do you have with your automated tests?
By understanding and implementing these concepts, you can ensure your test automation processes are secure, compliant, and capable of supporting multi-factor authentication in alignment with their Entra settings and policies. Let us know what is important to you in this space!
Let's Discuss!
Feel free to share your thoughts, ask questions, and provide feedback. Your contributions are valuable to the community!
Community Guidelines
Be respectful and kind to others.
Keep discussions relevant to testing and the Power Platform.
Provide constructive feedback and aim to support your fellow developers.
Happy discussing!
The text was updated successfully, but these errors were encountered:
Discussion Topic
Title:
Authentication in Power Apps Test Engine
Description
Overview:
Authentication is a critical component of the test automation process. The sample script employs browser-based authentication, which offers a range of options to authenticate with Microsoft Entra. This method generates a persistent browser cookie, allowing for non-interactive execution of subsequent tests. The management of these browser cookies is governed by the guidelines provided in the Microsoft Entra documentation on session lifetime and conditional access policies.
Details:
As the Power CAT Engineering team looked at the different authentication options for the CoE Starter Kit, we started with browser-based authentication for local testing. This approach works with the conditional access policies of our environments and allows a quick and less intrusive process to authenticate as different test personas.
As we look at our continuous integration and deployment process, we will evaluate certificate-based authentication to determine the correct mix of authentication and management trade-offs to select authentication options and what secret store is used to securely host the login credentials.
Key Questions
Resources
Authentication in Power Apps Test Engine
Call to Action
By understanding and implementing these concepts, you can ensure your test automation processes are secure, compliant, and capable of supporting multi-factor authentication in alignment with their Entra settings and policies. Let us know what is important to you in this space!
Let's Discuss!
Feel free to share your thoughts, ask questions, and provide feedback. Your contributions are valuable to the community!
Community Guidelines
Happy discussing!
The text was updated successfully, but these errors were encountered: