My OperaThe My Opera forums have been replaced with forums.opera.com. Please head over there to discuss Opera's products and features
See the new ForumsYou need to be logged in to post in the forums. If you do not have an account, please sign up first.
Windows authentication
Hi,does Opera support Windows authentication on websites?
We have an intranet website at work that need the Windows credentials.
Internet Explorer login automatically, but Opera does not.
Is there a way to enable this?
I can enter my credentials, but then I have to enter the credentials on every subdomain.
Thanks,
Mathijs
Is there a way to enable this option in Opera?
I know Internet explorer supports it on the corporate website, so I would think Opera should also.
According to Wikipedia, the server sends a WWW-Authenticate: Digest in the HTTP header, and Opera should answer that with a response.
I checked opera:config, and the option "Enable NTLM" is checked.
I know Internet explorer supports it on the corporate website, so I would think Opera should also.
According to Wikipedia, the server sends a WWW-Authenticate: Digest in the HTTP header, and Opera should answer that with a response.
I checked opera:config, and the option "Enable NTLM" is checked.
I have a similar problem. On most of our corporate intranet sites I can get an authentication popup, but for our wiki site I just get the following error:
Forbidden
You don't have permission to access / on this server.
Apache/2.2.3 (CentOS) Server at wiki.xxxx.com Port 80
This is the one thing that's keeping me from promoting Opera, as we use this resource all the time, and it's a huge pain to have to jump to FF or IE instead.
Forbidden
You don't have permission to access / on this server.
Apache/2.2.3 (CentOS) Server at wiki.xxxx.com Port 80
This is the one thing that's keeping me from promoting Opera, as we use this resource all the time, and it's a huge pain to have to jump to FF or IE instead.
"Forbidden" is a code, specifically number 403, sent by the server.
If it was trying to authenticate you it would be using code "401" which would trigger the authentication dialog.
Without knowing what the server actually sends I would have no further idea about what is going on. It might even be browser sniffing and a Catch-22 cookie.
If it was trying to authenticate you it would be using code "401" which would trigger the authentication dialog.
Without knowing what the server actually sends I would have no further idea about what is going on. It might even be browser sniffing and a Catch-22 cookie.
Sincerely,
Yngve N. Pettersen
Yngve N. Pettersen
vgoolmathijs: Seems I missed your post. Sorry.
The Digest Authentication mechanism for Single Sign-on (SSO) is supported in Opera, it is the server(s) that have to send the right information to the client.
Regarding SSO for NTLM/Negotiate, I actually consider that too dangerous since we have no reliable way to distinguish a site that you want to have that password, and one that tries to phish it (It might be possible to abuse such information, even if NTLM/Negotiate uses digest methods).
The Digest Authentication mechanism for Single Sign-on (SSO) is supported in Opera, it is the server(s) that have to send the right information to the client.
Regarding SSO for NTLM/Negotiate, I actually consider that too dangerous since we have no reliable way to distinguish a site that you want to have that password, and one that tries to phish it (It might be possible to abuse such information, even if NTLM/Negotiate uses digest methods).
Sincerely,
Yngve N. Pettersen
Yngve N. Pettersen