basic-authentication

About to open up a public api with OAuth access, no problem with that. Main site uses the api but with basic authentication instead (restricted for our internal ip range) Next step is to plan a mobile application but how should one handle authentication there? First thought was to create a special log in screen just for our appid to make it look like authentication (instead of authorization) but it would not be very hard to revers engineer our appid. How does (for example) facebook handle log in within the facebook iphone app? Look and feel says they're using authentication but if so, how do

I've googled a lot about the problem, but still did not find, why it is happening. When user cancels BASIC auth form in browser, blank page is appeared. 401 page is setup in Tomcat webapp, in Firebug i can see 401 Unauthorized. Maybe some header is missing in response? Please help! Thanks a lot in advance. UPDATE I think, my post is not informative enough: there is also combination of BASIC auth together with Spring Kerberos auth, and when blank page is appeared, headers are: WWW-Authenticate Negotiate Basic realm="MyRealm" Enabling Kerberos Authentication in Firefox . Setup params network

I've created a BasicAuthFilter and it has this signature: @Override public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException, ServletException This is working if someone calls the filter with an Authorization header set the right way. But, if someone on chrome or firefox visits the url like this: http://username:password@localhost:8888 The browsers are not populating the Authorization header with that information (which surprised me). I looked at the information sent by chrome and the username and password are in the request URL but nowhere

I am trying to connect to solr using solrj. My solr instance runs in jetty and is protected with basic authentication. I found these links that contain relevant information. http://grokbase.com/t/lucene/solr-user/1288xjjbwx/http-basic-authentication-with-httpsolrserver Preemptive Basic authentication with Apache HttpClient 4 However, I still get the following exception: Caused by: org.apache.http.client.ClientProtocolException at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:822) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java

I have this application that consists of a REST back-end intended to servicing requests from an HTML5/JavaScript client (which I'm also building). I'm planning on implementing an authentication mechanism that uses Basic Authentication where the JavaScript client would store the Base64-encoded user's credentials for the duration of a session. These credentials would be sent with each REST request in the "Authorization: Basic" header. All the conversation between the JavaScript client and the REST backend would occur over HTTPS. I'm know that's a performance drawback in itself as it adds the

I have an application that needs to integrate with one of SharePoint's web services. This web service cannot be accessed freely and needs authentication. As such, the standard wsdl2java Maven plugin in my application gives an HTTP 401 error when the generate-sources phase is executed. Is there a way to setup Maven/POM so that I can provide a user/password that will generate the stubs? I have come across some answers saying this is not possible but all answers are older than 1 year. I haven't found if Maven have issued an update on this. One option is to save a local copy of the WSDL (as