We have a custom application that makes web service requests. Does DACS require web services to be accessed using a browser?
No. Any user agent that talks HTTP to a web server, whether it’s a standard browser or some other program (such as a thick client or middleware), should be capable of obtaining DACS credentials and sending them as an HTTP cookie. For example, a Java/JSP application has been written that uses DACS entirely for its user authentication and access control. Once a user is authenticated and obtains a cookie, a DACS service is called by the application to identify the user and obtain his application-specific roles. DACS can work with the neon library, for instance, so that any application based on it should be able to authenticate users using Basic Auth through DACS. Because Subversion uses neon, we are using DACS to supply authentication and authorization for it. DACS supports “least common denominator” user agents. User agents need only support SSL and (for full functionality) the Netscape HTTP cookie standard, and be configured appropriately. Browsers without client-side certificates, appl
Related Questions
- What are the methodologies followed by RamsCorp in the process of web application designing and custom software development?
- We have a custom application that makes web service requests. Does DACS require web services to be accessed using a browser?
- How scalable is the Web Service (in terms of volume of service requests or no. of users)?
