Is it possible to use some sort of stateless authentication to control access to the site front end?
For example oAuth or openID (is this stateless)?
The use case is we are trying to work out a way to authenticate users of an iOS/Android app that will interface with an existing EE site.
EDIT: I think my original question may have been badly phrased. What we were looking for was a means to use HTTP authentication so an iPhone app could interface with the EE front end. Apparently if we used the regular EE authentication this might cause issues getting the app approved by Apple. They prefer "native" over "web"
I feel the need to clarify the reason behind this authentication requirement.
Its more about REST best-practices than getting the app Approved.
REST is by nature stateless (see here: en.wikipedia.org/wiki/Representational_state_transfer), however EE uses Session-based authentication. Turning on Basic HTTP Auth allows us to authenticate statelessly with the API rather than play around with a session cookie on the client side. Also worth noting that the libraries being used on the clients-side have nice support for Basic HTTP Auth, ie: http://cocoadocs.org/docsets/AFNetworking/1.3.1/Classes/AFHTTPClient.html#//api/name/setAuthorizationHeaderWithUsername:password:
In terms of Approval, wrapping a web view in a thin native shell might get the app rejected so consuming the data via REST and caching/displaying it natively is the best option.