Nah, grep is good. I just hadn't thought of it. Thanks for the
information and the help.
Cris
********************************
Cris Ewing
CME and Telehealth Web Services
Department of Radiology Web Services
University of Washington
School of Medicine
Work Phone: (206) 685-9116
Home Phone: (206) 365-3413
E-mail: [EMAIL PROTECTED]
*******************************
On Wed, 22 Nov 2006, Jens Vagelpohl wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 22 Nov 2006, at 00:06, cristopher pierson ewing wrote:
As the mapping tells you, the plugin responsible for getting these
credentials is "credentials_basic_auth", which is most likely a
HTTPBasicAuthHelper plugin, and you will see it right in your
PluggableAuthService object.
Again, you are right. The only question I have remaining is how the
'extractor' key in the credentials gets set. I've looked up the interface
for this method, and looked up the method being used in the
HTTPBasicAuthHelper.py file, and the tuple that method returns, called
'cred' doesn't contain such a key. I'm just curious here, trying to get a
handle on the logical flow of the authentication process. My PAS plugin
works well with only an authenticateCredentials method.
The place where the "extractor" key is set is not within the plugin itself,
it's not very obvious. If you take a look at the _extractUserIds method on
the PluggableAuthService object itself you'll see how the
PluggableAuthService iterates over the available credentials extraction
modules and then adds the key to the credentials mapping for any extraction
attempt that does return credentials.
This might seem crude to most people, but for questions like this I always
use "grep" to find out where the keyword is referenced.
jens
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFFY5eqRAx5nvEhZLIRAjbEAJ9ydYWuXIAWe6X2fgD534GHLy+HkQCglizN
oU7FwADmsmvjdVg4h7O9JKs=
=bQ3W
-----END PGP SIGNATURE-----
_______________________________________________
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
_______________________________________________
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
