I have been trying for a couple of days to verify an app on LinkedIn Developer portal, but getting an error each time I try. Is anyone else running into this? I've tried multiple apps and multiple computers.
Here are the steps:
Go to https://developer.linkedin.com/
Click on MyApps
Click Create App
Specify AppName, LinkedIn Page, Privacy Policy, Upload a Logo, Agree to terms. Click Create App
Request Access to Product: Sign In with Linked In
Go back to settings tab
Click Verify Button
Click Generate Url Button
Copy Url
Paste Url into browser window
Click Verify Button
Error pops up on bottom left of screen
I tried a few days later, and it worked. Must have been a prod issue on LinkedIn's servers
I have power BI embedded into my ASP.NET web application and is working for other developers and works on a previous computer but now I have a new computer without the last and it doesn't work.
after entering the web application, and clicking on the power BI button, for others, it shows a Office 365 login screen but for me, it appears and then disappears without giving the chance to enter in my details, therefore returning an error, of an unauthorized user.
https://i.imgur.com/820aqYz.png
I have tested and cleared cookies, session variables and any history from my computer so don't believe it is that.
Any advice would be appreciated.
When attempting to add a web reference to my MVC 4 project I do the following:
-Right click on project name and select "Add Service Reference..."
-Click on "Advanced..." button
-Click on "Add Web Reference..." button
-Enter the Web Services API WSDL address in the URL field
At this point it will search and then find the web service and ask me to authenticate the request, after agreeing to continue I am prompted with a login dialog, after entering the correct username and password it will often lock up. Sometimes it will re-display the login dialog and/or pop up some security confirmation boxes that read "Do you want to view only the webpage content that was delivered securely?" (Haven't been able to select Yes or No yet due to application hang around this time).
At this point I have to close the IDE and start the process over. I've tried 5+ times and have updated my system and rebooted.
Any ideas what could be causing this?
Thanks.
Turns out it just took a very very long time. When clicking on pop ups it would stop responding, I found if I waited long enough it would eventually let me make a selection, then the next box would hang. Whole process took well over 20min but eventually went through.
Not sure if this question should be deleted since technically there was no error, I'll leave it up to the mods.
Thanks.
I have an application deployed to IIS 6.1. When I enter my ASP app in Chrome, popup windows appear and I enter username and password to log into my app successfully. But when I login via Internet Explorer, I can't pass authentication. What could cause such behavior?
I'm not entirely sure exactly what behaviour you're after (you state in a comment that you've enabled anonymous access, however you appear happy with Chrome presenting a challenge response dialog to the user).
The issue is most likely that IE is passing your desktop credentials to the site, but they are being rejected, while Firefox/Chrome are not as doing this, hence the challenge response dialogs.
The options are:
Move the site out of the "Local Intranet" zone into (say) the "Trusted Sites" zone:
(For IE8 and below) Tools | Internet Options (IE9) Click on the Cog Icon | Internet Options
Switch to "Security" tab.
Click on "Trusted sites" and press the "Sites" button.
Add the Domain to the list - you may need to clear the "Require server verification (https:) for all sites in this zone" and OK.
Back on the Security tab, click the "Custom level..." button, scroll to the end of the Settings list, and make sure that the User Authentication | Logon is set to "Automatic Logon only in Intranet Zone".
Change all Intranet sites to prompt for credentials (I'd advise against this however, because it will cause you pain):
Open the Internet Options dialog as per steps 1.1 and 1.2 above.
Switch to the "Security" tab, and select "Local intranet".
Click on the "Custom level..." button, scroll to the end of the Settings list, and make sure that the User Authentication | Logon is set to "Prompt for user name and password".
Since the article linked by Xhalent shows a 404 now, I dug through Archive.org and found a version back from 2009.
I don't know how long this Archive.org version stays stable, so I'm quoting the article here:
Enabling NTLM Authentication in Firefox and Internet Explorer
This tip is useful for organizations who are standardized on Microsoft technologies (Active Directory, IIS, and ASP.NET) and need to provide minimal-intrusion authentication for their internal web applications. I was stumped for a long time on this one. Here’s the scenario:
All of my ASP.NET applications - at this point - are internal to the organization that I work for. We are a strictly Microsoft shop, and, because of this, I always leverage Active Directory in everyway possible. Well, this is great from my (a developer’s) perspective, as it means that I don’t have to build and maintain a login system. However, I recently started getting feedback from users across the country saying that they were being challenged with a login screen when they accessed the applications. This was okay, as they could still get in using their Active Directory accounts, but sometimes they had to append the domain to the beginning of their name, and it all became kind of a pain.
We are a diverse organization, in that we have many different network configurations. Some of our users are on high-quality T1 connections, while others are still on intermittent - at best - connections. Because of this disparity, I initially blamed the login problem on different network configurations (firewalls, distance to domain controller, etc.), but after doing a bit more research I found that the problem was actually browser related.
By the way, the Internet Explorer setting can also be implemented via group policy (thanks to Chris, James, and Marilyn for helping me figure this one out). Look in the registry at:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\Domains
So, here are the steps you need to take to enable NTLM pass-through authentication in Internet Explorer (6 & 7) and Firefox (2):
Internet Explorer
Note: These instructions apply to both IE 6 and IE 7, although there may be slight differences in the screenshots below.
Note2: For some reason, some of the entries that are added to the Local intranet zone seem to be persistent. You’ll delete them in the interface, close all the windows out, come back and they’ll reappear. The only way I found to permanently get rid of them was to manually delete the registry entry located at the location cited just above this section.
In Internet Explorer, click on Tools and select Internet Options.
Next, click on the Security tab at the top of the Internet Options window.
Once the contents of the Security tab are displayed, highlight Local intranet and click on the Sites button
In the Local intranet dialog that pops up, make sure that the last three boxes are checked and click on the Advanced button.
In the next dialog, type the following into the Add this website to the zone text box: "http://www.example.org" (without the quotes) and click on the Add button.
Note: If you’d like to enable Active Directory pass-through authentication for all the sites on a domain, type the following into the Add this website to the zone text box: "http://*.example.org" (without the quotes).
Mozilla Firefox
Note: These instructions have been tested on Firefox 2.0.0.1.
In the address bar of your Firefox browser window, type the following: "about:config" (without the quotes) and press Enter.
In the configuration page that displays, scroll down to the following entry: "network.automatic-ntlm-auth.trusted-uris" and double-click on it.
In the Enter string value that pops up, type "http://www.example.org" (without the quotes) into the text box and click OK.
Note: If you’d like to enable Active Directory pass-through
authentication for all of the sites on a domain, type the following
into the textbox: ".example.org_" (without the quotes).
You might need to ensure that the deployed site in the Local Intranet zone in IE. The following post discusses how to configure NTLM for IE and Firefox.
Whether you have anonymous access enabled (which you don't appear to), whether you have integrated security enabled, and which type of authentication you have selected for integrated security. Whether you have integrated security enabled in IE.
SUMMARY: When browsing an ASP.NET website using Windows Explorer, popup windows do not "borrow" the session cookie from the parent window.
DETAILS:
I'm working on an ASP.NET website (.NET 2.0). I use FormsAuthentication. It is a requirement to use cookies to handle the session.
On a page I have a button. When the user clicks it, a popup window is opened. The popup displays an ASPX page that uses session variables, previously set from the parent browser window. I've been testing the website using IE (6, 7, 8) and Firefox 2.0. On all these browsers, the popup window has access to the same session as the parent browser window and everything works ok.
I now have a bug raised by the client, stating that the popup window displays an error. Looking at the log file, I can see that it is a NullReferenceException at the moment the popup page tries to access the session variables. Talking with the client, he said that he opened the main website in Windows Explorer !!!
I've managed to recreate the issue on a test machine and saw that the popup is using a new session.
The machine must have Win XP an IE6 installed ! With IE7 the website works ok.
My suspicion here is that when opened from Windows Explorer (not that I fully understand what you mean by this), the session cookie that is being sent back is not stored anywhere and thus not available for the pop up window to include with its request. I don't see how you can get around this. Is it not possible to tell the client that this means of accessing the application is not supported?
I have seen the same issue with IE 8 , the issues does not occur in Firefox, Google Chrome or IE 6 . In my case I can see that the Session is actually working bu the Authentication terminates redirecting the user to the login page again for him to login...