basic-authentication

I am trying to consume a restful ws with basic auth. I did not import any cert into my keystore. When I use chrome plugin Advance Rest client to test it (using basic auth with base64 encoded username:pass). I can see the response back. So far so good. But when I develop Java code to consume this ws, I get SSL handsake failure: org.springframework.web.client.ResourceAccessException: I/O error: Received fatal alert: handshake_failure; nested exception is javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure at org.springframework.web.client.RestTemplate.doExecute

I am developing a REST API that I plan on using with a web and IOS app. I intend for this API to be private for sometime (private meaning I only want my web app and ios app to access the api). I have read about many different authentication methods but I am still to confused to select the appropriate authentication method for my API. From what I understand, oAuth2 is for allowing users to login to your APP using other service providers so that you can access the data on the respective service provider. I am accessing the data in my own API so I believe this does not apply to me? So, here is

I have an ASP.NET app that requires users to sign in with their domain accounts using Basic Authentication. The user can make a selection, then press a button. At some point after pressing the button is this code: WindowsIdentity.Impersonate(userIdentity.Token) . userIdentity is of type WindowsIdentity , and it was previously set to (WindowsIdentity)User.Identity . userIdentity is stored as a session variable, and I think that's because, after the button is pressed, the page containing this code is called via AJAX. When I hit this code, it works about 2/3 of the time, but 1/3 of the time, I

I've successfully installed GitLab for management of private repositories (it's quite awesome!). The problem I am having is by default, Gitlab login is presented when anyone hits my subdomain. I would like to protect the entire area with a basic_auth layer before the user gets the GitLab login screen. Unfortunately, this breaks my ability to push/pull from GitLab when it's enabled. my nginx config to enable basic_auth: auth_basic "Restricted"; auth_basic_user_file htpasswd; Any ideas on how I can enable basic_auth without breaking git / gitlab functionality? Add this to /etc/gitlab/gitlab.rb :

I have an embedded implementation of Jetty 7 running as a service and want to add basic authentication with no web.xml file for a servlet. I created my credentials using the steps described here I thought that I could create the server, create a security handler with basic authentication and attach a HashLoginService to the security manager. But I am clearly missing several things because I am never getting prompt for credentials. Below is the code. Any help would be greatly appreciated. server = new Server(port); server.addConnector(getSslChannelConnector(securePort)); server

Can anyone tell me, how can I get this browser authentication window ? This popup is part of the HTTP-Authentication . In order to get it, you need to enable it in your web server. As Wikipedia puts it: When the server wants the user agent to authenticate itself towards the server, it can send a request for authentication. This request should be sent using the HTTP 401 Not Authorized response code containing a WWW-Authenticate HTTP header. The WWW-Authenticate header for basic authentication (used most often) is constructed as following: WWW-Authenticate: Basicrealm="insert realm" That type of