From: barry <sla...@i1...> - 2002-01-10 17:43:00
|
Has anyone tried sharing user logins with other virtual hosts? Suppose I have my main slash site at www.domain.com, and suppose I have some other site integrated into the main site at say, tools.domain.com. Now suppose I want to allow users who are logged in to www to click straight through to tools (or type in the url or whatever), but if they are not logged in they should get some sort of appropriate error message and maybe the slash login page. Assumption 1: tools.domain.com is a perl module Could I just include the appropriate slash .pm files and use them to call the user database files/ user cookies, or is there a better way? Assumption 2: tools.domain.com is not written in perl at all Am I now restricted to using native cookie reading code and/or reproducing the slash .pm code in the local language? Any thoughts and ideas welcome, Thanks, Barry |
From: Chris N. <pu...@po...> - 2002-01-10 18:02:02
|
At 09:42 -0800 2002.01.10, barry wrote: >Has anyone tried sharing user logins with other virtual hosts? I've considered doing that with use.perl.org and other .perl.org systems. >Suppose I have my main slash site at www.domain.com, and suppose I have >some other site integrated into the main site at say, tools.domain.com. > >Now suppose I want to allow users who are logged in to www to click >straight through to tools (or type in the url or whatever), but if they are >not logged in they should get some sort of appropriate error message and >maybe the slash login page. > >Assumption 1: tools.domain.com is a perl module > >Could I just include the appropriate slash .pm files and use them to call >the user database files/ user cookies, or is there a better way? > >Assumption 2: tools.domain.com is not written in perl at all > >Am I now restricted to using native cookie reading code and/or reproducing >the slash .pm code in the local language? There are several ways to do it. One would be if they can share the same database: Brian says you can symlink database tables, so you could just symlink all your user tables from one to the other, if you like. That's sortof a hack. A way I was envisioning would be to make the Slash site your primary site, where users change their passwords and other information. Then set up a way for other sites to query for correct username/password (possibly through web services, or somesuch; I am right now exploring web services infrastructure for Slash). So a user goes to the other site, and either already has a cookie from the first site, or supplies a username/password; either way, the second site sends that information to the first site to verify it. Then the second site somehow stores that login information for a period of time, to verify that the user's cookie/username/password whatever are valid. There are other ways to do it, but this is the way I am considering currently. It can work with any other system, regardless of language, database, etc. -- Chris Nandor pu...@po... http://pudge.net/ Open Source Development Network pu...@os... http://osdn.com/ |
From: shane <sh...@lo...> - 2002-04-21 21:18:15
|
At 04:46 PM 4/20/2002 +0000, Leoncini Xavier wrote: >Hello, while I was upgrading my slash site from 2.0 to 2.2.5, >I used 2 different machines, the upgrade went smoothly, but >I have still a problem, >I used the new version as a beta for a while it thus was run as something >l;ike beta.nycircus.com, >while I was playing with it. In the meanwhile sttories started to get >archived and htlm file created. >When I switched from beta to official, all these archived file kept the >wrong variables and link, >also the templates were not stabilized, hence the stories look ugly when >directly accessed. > >I was wondering if there was a simple way to recreated all the archived >html files >to have them display correctly. >Thanks for any info, >Xavier If you change each stories status from 'archived' to 'dirty' that'll cause slashd to kickoff the process that will write the old stories to disk again. So that should make it write them w/ the newer templates and change the look of them. Shane |
From: Leoncini X. <xa...@ny...> - 2002-04-24 01:52:35
|
Thanks, do you know if I have to do that directly in the database, or there is another way from the admin menu which I could not find. What also happens is for instance, when I save a story, a few minutes later I notice a grammatical error, and update it, the story looks fine when processed by article.pl or index.pl, but the .shtml files are not updated (the story one and the index one), hence I still look stupid to any newcomer. shane wrote: > At 04:46 PM 4/20/2002 +0000, Leoncini Xavier wrote: > >> Hello, while I was upgrading my slash site from 2.0 to 2.2.5, >> I used 2 different machines, the upgrade went smoothly, but >> I have still a problem, >> I used the new version as a beta for a while it thus was run as >> something l;ike beta.nycircus.com, >> while I was playing with it. In the meanwhile sttories started to get >> archived and htlm file created. >> When I switched from beta to official, all these archived file kept >> the wrong variables and link, >> also the templates were not stabilized, hence the stories look ugly >> when directly accessed. >> >> I was wondering if there was a simple way to recreated all the >> archived html files >> to have them display correctly. >> Thanks for any info, >> Xavier > > > If you change each stories status from 'archived' to 'dirty' that'll > cause slashd to kickoff the process that will write the old stories to > disk again. So that should make it write them w/ the newer templates > and change the look of them. > > Shane > > > > > _______________________________________________ > Slashcode-general mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-general > -- xa...@ny... http://www.nycircus.com NYCircus.com: NYC Lifestyles |
From: Brian A. <br...@ta...> - 2002-01-10 18:02:04
|
On Thu, 2002-01-10 at 09:42, barry wrote: > Has anyone tried sharing user logins with other virtual hosts? Yes, do it all the time. > Suppose I have my main slash site at www.domain.com, and suppose I have > some other site integrated into the main site at say, tools.domain.com. You will need to user a cookie with .domain.com > Could I just include the appropriate slash .pm files and use them to call > the user database files/ user cookies, or is there a better way? Well, as long as Slash::Apache::User is around doing it thing you just need to use Slash::Utility to grab the current user and database. getCurrentUser() getCurrentDB() > Am I now restricted to using native cookie reading code and/or reproducing > the slash .pm code in the local language? Nope. We populate environmental variables with the values from $user and $form. So you can just pull the values from those. There will be data though that you will not be able to access, but its pretty small. -Brian -- _______________________________________________________ Brian Aker, br...@ta... Slashdot Senior Developer Seattle, Washington http://tangent.org/~brian/ http://askbrian.org/ _______________________________________________________ You can't grep a dead tree. |
From: Leoncini X. <xa...@ny...> - 2002-04-20 20:45:10
|
Hello, while I was upgrading my slash site from 2.0 to 2.2.5, I used 2 different machines, the upgrade went smoothly, but I have still a problem, I used the new version as a beta for a while it thus was run as something l;ike beta.nycircus.com, while I was playing with it. In the meanwhile sttories started to get archived and htlm file created. When I switched from beta to official, all these archived file kept the wrong variables and link, also the templates were not stabilized, hence the stories look ugly when directly accessed. I was wondering if there was a simple way to recreated all the archived html files to have them display correctly. Thanks for any info, Xavier -- xa...@ny... http://www.nycircus.com NYCircus.com: NYC Lifestyles |