none
Multi step Web Availability Test in Application insights

    Question

  • Hi ,

       I am new to Azure. I have developed Single step web availability tests which are working fine. Now ,i want to developer a Multi Step Web Availability test using Visual Studio 2017 Enterprise edition.

    https://github.com/uglide/azure-content/blob/master/articles/application-insights/app-insights-monitor-web-app-availability.md

    I straight forward added the links into Add request and start testing. Later on , i added it to Azure Availability Test and it worked.

    My Questions is :

    I am not a developer and want to authenticate some pages. I read out it required to authenticate through token. Can you please guide how a non developer person can go for this. any hint. Is there coding involved or you can just put it as configurations.


    WSBukhari

    Monday, January 7, 2019 9:57 AM

Answers

  • Hi IbrahimUmar,

    Thank you for exploring Azure Application Insights. For Multi Step availability test involving sign in, it depends on what kind of authentication your application supports and you should create your web test accordingly. Below are the possible ways you can deal with Sign in.

    • Simple username and password: Just record a web test in the usual way. Delete cookies first.
    • SAML authentication. For this, you can use the SAML plugin that is available for web tests.
    • Client secret: If your app has a sign-in route that involves a client secret, use that. Azure Active Directory provides this.
    • Open Authentication - for example, signing in with your Microsoft or Google account.

    If you want to explore Client Secret option , we do not have out of box option to enable it directly. See if below steps can help to achieve it.

    • Ensure you have Azure AD Directory or use an existing one.
    • Ensure your application is registered with Azure AD
    • Ensure your application is provide permissions with in App Registrations.
    • Get token from AAD using client secret (AppKey).
    • Extract bearer token from response.
    • Call API using bearer token in the authorization header.

    Hope this helps , reach out us if you need any further information. Thank you

    Additional documentation reference -  

    https://docs.microsoft.com/en-us/azure/azure-monitor/app/monitor-web-app-availability#dealing-with-sign-in

    https://azure.microsoft.com/en-us/blog/creating-a-web-test-alert-programmatically-with-application-insights/

     

     

    Tuesday, January 15, 2019 3:20 AM
    Owner

All replies

  • Like , i want that all sub pages of these main links could also be tested. If it required authentication with token , how it is possible.

    like how can i deal with authentication with Token. Where is to mention that or it will pick up randomly? HOW?


    WSBukhari


    • Edited by IbrahimUmar Monday, January 7, 2019 11:06 AM Modify
    Monday, January 7, 2019 11:01 AM
  • Hi IbrahimUmar,

    Thank you for exploring Azure Application Insights. For Multi Step availability test involving sign in, it depends on what kind of authentication your application supports and you should create your web test accordingly. Below are the possible ways you can deal with Sign in.

    • Simple username and password: Just record a web test in the usual way. Delete cookies first.
    • SAML authentication. For this, you can use the SAML plugin that is available for web tests.
    • Client secret: If your app has a sign-in route that involves a client secret, use that. Azure Active Directory provides this.
    • Open Authentication - for example, signing in with your Microsoft or Google account.

    If you want to explore Client Secret option , we do not have out of box option to enable it directly. See if below steps can help to achieve it.

    • Ensure you have Azure AD Directory or use an existing one.
    • Ensure your application is registered with Azure AD
    • Ensure your application is provide permissions with in App Registrations.
    • Get token from AAD using client secret (AppKey).
    • Extract bearer token from response.
    • Call API using bearer token in the authorization header.

    Hope this helps , reach out us if you need any further information. Thank you

    Additional documentation reference -  

    https://docs.microsoft.com/en-us/azure/azure-monitor/app/monitor-web-app-availability#dealing-with-sign-in

    https://azure.microsoft.com/en-us/blog/creating-a-web-test-alert-programmatically-with-application-insights/

     

     

    Tuesday, January 15, 2019 3:20 AM
    Owner