|
Beat me to it, Kevin.
Sorry for the confusion. My point was meant to be in regards to "single
sign-on" which involves BROWSER "redirects" back and forth between the
server which which performs trusted "authentication" and another which
provides services; Any protocol which assumes the "client" is a browser and
manipulates the browser DOM.
Some of the previous references about oAuth were for single sign-on
implementations which manipulate the browser's DOM.
I understanding that oAuth and similar SAML based protocols are fairly
loose standards, which may be adapted for general purpose "authentication",
including for web services.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.