[Zope] Q: LoginManager and SQL-US?

Tue, 13 Jun 2000 11:29:48 -0400

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01BFD54C.387A2D28
Content-Type: text/plain;
	charset="iso-8859-1"

Ok, I've got this legacy database app (VisualBasic and Access - Bleck!)
that I'm moving to Apache/Zope/PostgreSQL.  One of the existing database
tables is user info, i.e. userid, password, real name, an "account
disabled" boolean, etc.

I've figured out a really stupid way to "solve" the problem, essentially
doing queries against the user table and having conditionals in every
DTML object to determine if the user should be there or not.  (Actually,
I negated some of that silliness by incorporating SQLSession into the
mix.)  Still, I'm faced with needing some way to check the user/session
against each requested object.  And no, there's not much access
granularity here - the user should either have access to the whole
folder, or not.

LoginManager looks promising, but I'm still enough of a Zope newbie that
I've hit a bit of a roadblock, boiling down (boiled roadblock?!?) to 2
fundemental questions:

	1. Can LoginManager be (easily?) made to meet my specific need?
	2. Has anyone done an SQL UserSource yet, or can anyone
	   give me a clue how to make one?

I've tried "creating" another US, but after that Zope just sits there,
quietly mocking me.  I did read the API stuff and that actually makes
a little sense to me, but I don't know what types of objects (or
external methods?) would need to be created as part of a new US
interface.  In other words, I more or less understand the API calls, I
can do SQL queries in my sleep, but how does one tie it all together
into a new US?  Does it involve (*shudder*) writing Python? ;)

I'd be happy to share back any useful results of this exercise.

Thanks for any help,
	Charlie

-- 
Charlie Wilkinson - TRIS Development Systems Administrator 
IS:SD:CT:CC:TD
Phone: 202-283-3241 
MSMail:   Charlie E Wilkinson <mailto:Charlie E Wilkinson>  
SMTP:  cwilkins@tris.irs.gov <mailto:cwilkins@tris.irs.gov>  
Home:  cwilkins@boinklabs.com 
This message constructed from 90% post-consumer electrons. 

------_=_NextPart_001_01BFD54C.387A2D28
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2650.12">
<TITLE>Q: LoginManager and SQL-US?</TITLE>
</HEAD>
<BODY>

Ok, I've got this legacy database app (VisualBasic =
and Access - Bleck!)
 that I'm moving to Apache/Zope/PostgreSQL.&nbsp; One =
of the existing database
 tables is user info, i.e. userid, password, real =
name, an &quot;account
 disabled&quot; boolean, etc.

<P><FONT SIZE=3D2>I've figured out a really stupid way to =
&quot;solve&quot; the problem, essentially</FONT>
<BR><FONT SIZE=3D2>doing queries against the user table and having =
conditionals in every</FONT>
<BR><FONT SIZE=3D2>DTML object to determine if the user should be there =
or not.&nbsp; (Actually,</FONT>
<BR><FONT SIZE=3D2>I negated some of that silliness by incorporating =
SQLSession into the</FONT>
<BR><FONT SIZE=3D2>mix.)&nbsp; Still, I'm faced with needing some way =
to check the user/session</FONT>
<BR><FONT SIZE=3D2>against each requested object.&nbsp; And no, there's =
not much access</FONT>
<BR><FONT SIZE=3D2>granularity here - the user should either have =
access to the whole</FONT>
<BR><FONT SIZE=3D2>folder, or not.</FONT>
</P>

<P><FONT SIZE=3D2>LoginManager looks promising, but I'm still enough of =
a Zope newbie that</FONT>
<BR><FONT SIZE=3D2>I've hit a bit of a roadblock, boiling down (boiled =
roadblock?!?) to 2</FONT>
<BR><FONT SIZE=3D2>fundemental questions:</FONT>
</P>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1. Can =
LoginManager be (easily?) made to meet my specific need?
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2. Has =
anyone done an SQL UserSource yet, or can anyone
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; give me a clue how to make one?

I've tried &quot;creating&quot; another US, but after =
that Zope just sits there,
 quietly mocking me.&nbsp; I did read the API stuff =
and that actually makes
 a little sense to me, but I don't know what types of =
objects (or
 external methods?) would need to be created as part =
of a new US
 interface.&nbsp; In other words, I more or less =
understand the API calls, I
 can do SQL queries in my sleep, but how does one tie =
it all together
 into a new US?&nbsp; Does it involve (*shudder*) =
writing Python? ;)

<P><FONT SIZE=3D2>I'd be happy to share back any useful results of this =
exercise.</FONT>
</P>

<P><FONT SIZE=3D2>Thanks for any help,</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>Charlie</FONT>
</P>

-- 
 Charlie Wilkinson - TRIS Development Systems =
Administrator 
 IS:SD:CT:CC:TD
 Phone: 202-283-3241 
 MSMail:&nbsp;&nbsp; Charlie E Wilkinson &lt;<A =
HREF=3D"mailto:Charlie">mailto:Charlie</A> E Wilkinson&gt;&nbsp; =

 SMTP:&nbsp; cwilkins@tris.irs.gov &lt;<A =
HREF=3D"mailto:cwilkins@tris.irs.gov">mailto:cwilkins@tris.irs.gov</A>&g=
t;&nbsp; 
 Home:&nbsp; cwilkins@boinklabs.com 
 This message constructed from 90% post-consumer =
electrons.

</BODY>
</HTML>
------_=_NextPart_001_01BFD54C.387A2D28--