Visual Studio- Web Tests failed with message " Context parameter '$HIDDEN1.NAP' not found in test context " and web test redirecting to login page - web-testing

our web test are working fine earlier , when we have migrated our login to AAD, web tests failed with the below reasons:
Request failed: Context parameter '$HIDDEN1.NAP' not found in test context
Redirecting to Login page.

Related

Cypress test exit test cases after redirecting to external login

my application is using IBM w3 login authentication https://preprod.login.w3.ibm.com/
if I'm trying to hit my base URL cy.visit('/baseuRl') it redirects to https://preprod.login.w3.ibm.com/ w3 login to authenticate me.
after redirecting back to my application I found cypress exists
it there any workaround to bypass w3-Auth handle it?

There was an error getting a Chat authorization token. Refresh and try again

I recently created a chatbot via http://dev.botframework.com/bots (the page initially displayed the info that I did not have any bots). The form redirected me to Azure Portal where I chose a new "Web App Bot" option. I also created all required resources (RG and even setup a new tenant with admin rights).
After successful deployment I got the following issues:
Test in Web Chat in bot settings (Azure Portal) shows "There was an error getting a Chat authorization token. Refresh and try again."
Channels in bot settings shows "Unable to find the bot with the specified id."
dev.botframework.com/bots shows there are no bots created
Have anyone had this issue?
I also get same issue and it got resolved, Please refer below url , it may help you as well.
https://github.com/Microsoft/BotFramework-Emulator/issues/1068

WSO2 IS SAML2.0 Deactivates user after single login

I downloaded WSO2 IS, took care of all the prerequisites and started it using "wso2server.bat --run" command.
It's running and I am able to configure it in Management Console as Identity Provider (SAML 2.0). I also added my app as Service Provider (SAML 2.0). SSO seems to be working - I navigate to my app, it redirects to WSO2 IS where I log in using default admin/admin. I am then redirected to assertion service in my app when I am authenticating a user. Everything great so far!
The problem is that when I close the browser (using incognito mode) and try to repeat that process and login to WSO2 IS using the same user (admin/admin) I get error message:
"Login failed! Please recheck the username and password and try again."
I also get similar message in console:
[2018-02-08 15:57:39,258] ERROR {org.wso2.carbon.identity.scim.common.listener.SCIMUserOperationListener} - Trying to login from an inactive account of user: admin
How is that possible? It looks like the second I use given user during SSO process - that account gets deactivated. I can't even login to WSO2 IS Management Console.
I did not change any configuration other than mentioned above.
I would appreciate any help.

Facebook login fails on deployed Meteor application

I'm using the extended accounts package 'accounts-facebook'. When I run my application locally, the login authentication procedure works after adding 'http://localhost:3000/_oauth/facebook?close' under Valid OAuth redirect URIs.
After deploying the application however, the login pop-up gives no error, but remains blank without completing the authentication procedure. I've tried adding 'http://www.algoloom.com/_oauth/facebook?close' and loads of possible variations to this, as some other forum discussions suggest, but the login procedure is never completed.
While I was testing my application in its deployed version, I managed to get Facebook login working by changing its ROOT_URL to 'http://www.algoloom.com:3010', in combination with 'http://www.algoloom.com:3010/_oauth/facebook?close' as a redirect URI. Now that I've set nginx to redirect to port 3010 by default, the 3010 disappears from the main website URL. As a result I've also set my ROOT_URL to 'http://www.algoloom.com'. This works fine for any other website functionality, but I can't seem to fix my my issues with Facebook login.
Any ideas on how to solve this?

Test OAuth Login Redirection for Facebook

I'm building an ASP.NET MVC application that shows information from Facebook. However, if I'm debugging the website locally without a public HTTP endpoint, how can I test the authentication to grab the OAuth token to ensure my app can pull the correct information?
If you mean running in localhost . . . take a look at this question:
Running Facebook application on localhost