Re: [SOGo] SSO using vulture

2011-06-08 Thread Sébastien Posé

Le 09/06/2011 10:23, Fabrice Durand a écrit :

Try with this TransHandler.pm and be sure that "Follow the post return"
in your app is desactivate

Regards

Le 9 juin 2011 08:16, Sébastien Posé mailto:sebastien.p...@ac-reunion.fr>> a écrit :

Le 08/06/2011 18:30, Fabrice Durand a écrit :

Hi, what a coincidence,
Yesterday I fixed this problem between Sogo and vulture.
Which version of vulture do you use and can you send me the
TransHandler.pm file, I make you a patch.

Regards
Fabrice Durand

Le 8 juin 2011 14:34, Sébastien Posé
mailto:sebastien.p...@ac-reunion.fr>
>> a écrit :


Hi,

I'm trying to use sogo throw vulture. I would like vulture
authenticates my users by sending their login and password
to the
sogo's connection page (SSO feature).

I'm able to authenticate users but they are redirected to
/SOGo/connect and got:
{"grace": -1, "expire": -1}

If I remove /connect and refresh, I'm redirected to
/SOGo/so/sebastien.pose/Mail/view and everything is ok.

Has anyone encountered a similar problem?

Thanks.
--
Sébastien Posé
Division des Services Informatiques
Rectorat de la Réunion
--
users@sogo.nu  >

https://inverse.ca/sogo/lists



Hi,

I'm using vulture 1.99

Thank you.


--
Sébastien Posé
Division des Services Informatiques
Rectorat de la Réunion
--
users@sogo.nu 
https://inverse.ca/sogo/lists




It works like a charm.

Thank you.

--
Sébastien Posé
Division des Services Informatiques
Rectorat de la Réunion
--
users@sogo.nu
https://inverse.ca/sogo/lists


Re: [SOGo] SSO using vulture

2011-06-08 Thread Fabrice Durand
Try with this TransHandler.pm and be sure that "Follow the post return" in
your app is desactivate

Regards

Le 9 juin 2011 08:16, Sébastien Posé  a écrit
:

> Le 08/06/2011 18:30, Fabrice Durand a écrit :
>
>> Hi, what a coincidence,
>> Yesterday I fixed this problem between Sogo and vulture.
>> Which version of vulture do you use and can you send me the
>> TransHandler.pm file, I make you a patch.
>>
>> Regards
>> Fabrice Durand
>>
>> Le 8 juin 2011 14:34, Sébastien Posé > > a écrit :
>>
>>
>>Hi,
>>
>>I'm trying to use sogo throw vulture. I would like vulture
>>authenticates my users by sending their login and password to the
>>sogo's connection page (SSO feature).
>>
>>I'm able to authenticate users but they are redirected to
>>/SOGo/connect and got:
>>{"grace": -1, "expire": -1}
>>
>>If I remove /connect and refresh, I'm redirected to
>>/SOGo/so/sebastien.pose/Mail/view and everything is ok.
>>
>>Has anyone encountered a similar problem?
>>
>>Thanks.
>>--
>>Sébastien Posé
>>Division des Services Informatiques
>>Rectorat de la Réunion
>>--
>>users@sogo.nu 
>>
>>https://inverse.ca/sogo/lists
>>
>>
>>
> Hi,
>
> I'm using vulture 1.99
>
> Thank you.
>
>
> --
> Sébastien Posé
> Division des Services Informatiques
> Rectorat de la Réunion
> --
> users@sogo.nu
> https://inverse.ca/sogo/lists
>


TransHandler.pm
Description: Binary data


Re: [SOGo] SSO using vulture

2011-06-08 Thread Sébastien Posé

Le 08/06/2011 18:30, Fabrice Durand a écrit :

Hi, what a coincidence,
Yesterday I fixed this problem between Sogo and vulture.
Which version of vulture do you use and can you send me the
TransHandler.pm file, I make you a patch.

Regards
Fabrice Durand

Le 8 juin 2011 14:34, Sébastien Posé mailto:sebastien.p...@ac-reunion.fr>> a écrit :

Hi,

I'm trying to use sogo throw vulture. I would like vulture
authenticates my users by sending their login and password to the
sogo's connection page (SSO feature).

I'm able to authenticate users but they are redirected to
/SOGo/connect and got:
{"grace": -1, "expire": -1}

If I remove /connect and refresh, I'm redirected to
/SOGo/so/sebastien.pose/Mail/view and everything is ok.

Has anyone encountered a similar problem?

Thanks.
--
Sébastien Posé
Division des Services Informatiques
Rectorat de la Réunion
--
users@sogo.nu 
https://inverse.ca/sogo/lists




Hi,

I'm using vulture 1.99

Thank you.

--
Sébastien Posé
Division des Services Informatiques
Rectorat de la Réunion
--
users@sogo.nu
https://inverse.ca/sogo/listspackage Vulture::TransHandler;

use Apache2::Const -compile => qw(OK REDIRECT FORBIDDEN);
use Apache2::RequestRec ();
use Apache2::RequestIO ();
use Apache2::Reload;
use Apache2::Log;
use APR::URI;
use APR::Table;
use APR::URI;
use APR::SockAddr;
use HTTP::Request;
use Apache2::RequestUtil ();
use LWP::UserAgent;
use Apache2::Connection;
use Apache::SSLLookup;
use IPC::Run qw(run);

use Vulture qw(&get_app $proto &read_conf &get_cookie &session);

use Data::Dumper;

sub REMOTE_ADDR { 1 };
sub SCRIPT { 20 };
sub Vulture_portail { 1 };

my %headers_vars = (
		2 => 'SSL_CLIENT_I_DN',
		3 => 'SSL_CLIENT_M_SERIAL',
		4 => 'SSL_CLIENT_S_DN',
		5 => 'SSL_CLIENT_V_START',
		6 => 'SSL_CLIENT_V_END',
		7 => 'SSL_CLIENT_S_DN_C',
		8 => 'SSL_CLIENT_S_DN_ST',
		9 => 'SSL_CLIENT_S_DN_Email',
		10 => 'SSL_CLIENT_S_DN_L',
		11 => 'SSL_CLIENT_S_DN_O',
		12 => 'SSL_CLIENT_S_DN_OU',
		13 => 'SSL_CLIENT_S_DN_CN',
		14 => 'SSL_CLIENT_S_DN_T',
		15 => 'SSL_CLIENT_S_DN_I',
		16 => 'SSL_CLIENT_S_DN_G',
		17 => 'SSL_CLIENT_S_DN_S',
		18 => 'SSL_CLIENT_S_DN_D',
		19 => 'SSL_CLIENT_S_DN_UID',
		   );

sub rewrite {
	my ($r, $line, $uri) = @_;

	my ($exp, $rule) = split (/=>/, $line);

	$rule =~ s/\s*//g;
	$exp =~ s/\s*//g;

	$line =~ /\[([A-Z0-9]+)\]/;
	my ($cond) = $1;
	return unless ($rule and $exp and ($$uri.($r->args ? "?".$r->args : "")) =~ /$exp/x);
	return if ($cond =~ /,NOCERT$/ and $r->ssl_lookup('SSL_CLIENT_M_SERIAL'));
	return if ($cond eq "H" or $cond eq "MH" or $cond eq "F" or $cond eq "UH" or $cond eq "L" or $cond eq "RH" or $cond eq "HL" or $cond eq "HP");

	$rule =~ s/\[$cond\]//;
	$cond =~ s/,NOCERT$//;

	if ($cond =~ /([0-9]+)/) {
		$r->status($1);
		return $1;
	}

	if ($$uri =~ /$exp/x) { # Load $1 $2
		$$uri = eval "\"$rule\"";
	}
	return $cond;
}


sub rewrite_uri { # Fonction de reécriture d'url pour étre valide depuis internet
   my ($r, $app, $uri, $real_post_url, $log) = @_;

	if ($uri !~ /^(http|https):\/\/(.*)/ ) {
		my $rewrite_uri2 = APR::URI->parse($r->pool, $real_post_url);
		my $path = $rewrite_uri2->path();
		if ($uri =~ /^\/(.*)/) {
			$rewrite_uri2->hostname($app->{'name'});
			$rewrite_uri2->path($uri);
		}
		else {
			$path =~ s/[^\/]+$/$uri/g;
			$rewrite_uri2->path($path);	
		}
	$uri = $rewrite_uri2->unparse;
   }
   my $rewrite_uri = APR::URI->parse($r->pool, $uri);
   $rewrite_uri->hostname($app->{'name'});
   $rewrite_uri->scheme('http');
   $rewrite_uri->scheme('https') if $r->is_https;
   $rewrite_uri->port($r->connection->local_addr->port);
   return $rewrite_uri->unparse;
} 

sub handler {
	my $r = Apache::SSLLookup->new(shift);

	my $uri = $r->uri;
	my $server;
	my $dbh = DBI->connect($r->dir_config('VultureDSN'));
	my $log = $r->server->log;

	my $vulture_portail = 0;
	my $vulture_portail_uri = 0;


	if ($r->unparsed_uri =~ /static\/(.*)/) {
		$log->debug("Serving $1");
		$r->filename("/var/www/vulture/conf/static/$1");
		return Apache2::Const::OK;
	}

	my $app = get_app($log, $r->hostname, $dbh, $r->dir_config('VultureID')) if ($r->unparsed_uri !~ /vulture_app/ and $r->unparsed_uri !~ /vulture_logout/);

	if ($app and $app->{up}) {
		my ($id) = get_cookie($r->headers_in->{Cookie}, 'vulture_app=([^;]*)') if ($app->{auth});
		my ($vulture_portail) = get_cookie($r->headers_in->{Cookie}, 'vulture_portail=([^;]*)');

		my %session;
		my %session_referer;
		session(\%session, $app->{timeout}, $id) if ($id);

		if ($r->unparsed_uri =~ /vultureportail=(.*)/) {
			my ($vulture_portail_uri) = $1;
		}

		#Si il y a quelque chose dans cette variable c'est qu'il faut repasser pas le ResponseHandler.pm
		if ($session{reponse}) {
			return Apache2::Const::OK;
		}
		if (($session{_session_id} and $session{post}) or !$app->{'auth'}) {
			$r->user($session{user});
			my $sth = $dbh->p

[SOGo] BTS activities for Wednesday, June 08 2011

2011-06-08 Thread SOGo reporter
Title: BTS activities for Wednesday, June 08 2011





  
BTS Activities

  Home page: http://www.sogo.nu/bugs
  Project: SOGo
  For the period covering: Wednesday, June 08 2011

  
  
idlast updatestatus (resolution)categorysummary
	
	
	  
	
1251
	2011-06-08 13:24:32
	updated (open)
	Web Address Book
	Import of exported LDIF don't work with Umlauts
	
	  
	
  
  




Re: [SOGo] Delete users from database

2011-06-08 Thread Paul van der Vlis
Op 07-06-11 23:47, Alan Bover schreef:
> Hi, I missed an utility in SOGo for delete the users from the database (for
> example, if a user-account gets corrupted, or a user leaves a company, etc).
> That's why I created a simple python script that I share with you. For run it,
> MySQLdb module for python needs to be installed.

Nice!  Just what I need ;-)

But it's an interactive shell and I would like to give direct commands.
This works in a bash script:

sogodel 

Re: [SOGo] view filter: all future events, recurring events dont show up

2011-06-08 Thread Wolfgang Sourdeau
Le Mercredi 8 Juin 2011 03:38 EDT,  a écrit:

> Hi,
>
> Is this a "feature" or a bug? I have the latest nightly build installed on
> centos with postgres and LDAP for authentication. I am using the Web interface

To complete Francis's response, I would add that this was removed to avoid the 
server looping indefinitely until the end of time while computing infinite 
occurrences. Also, this avoids filling the list too much, which can cause 
performance issues on certain browsers.
--
Wolfgang Sourdeau :: +1 (514) 447-4918 ext. 125 :: wsourd...@inverse.ca
Inverse inc. Leaders behind SOGo (sogo.nu) and PacketFence (www.packetfence.org)


-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] SSO using vulture

2011-06-08 Thread Fabrice Durand
Hi, what a coincidence,
Yesterday I fixed this problem between Sogo and vulture.
Which version of vulture do you use and can you send me the
TransHandler.pmfile,
I make you a patch.

Regards
Fabrice Durand

Le 8 juin 2011 14:34, Sébastien Posé  a écrit
:

> Hi,
>
> I'm trying to use sogo throw vulture. I would like vulture authenticates my
> users by sending their login and password to the sogo's connection page (SSO
> feature).
>
> I'm able to authenticate users but they are redirected to /SOGo/connect and
> got:
> {"grace": -1, "expire": -1}
>
> If I remove /connect and refresh, I'm redirected to
> /SOGo/so/sebastien.pose/Mail/view and everything is ok.
>
> Has anyone encountered a similar problem?
>
> Thanks.
> --
> Sébastien Posé
> Division des Services Informatiques
> Rectorat de la Réunion
> --
> users@sogo.nu
> https://inverse.ca/sogo/lists
>
-- 
users@sogo.nu
https://inverse.ca/sogo/lists

[SOGo] Sogo Integrator behaviour

2011-06-08 Thread Matthieu ROGER
Title: Signature Matthieu ROGER


  
  
Hello,

One question about Sogo Integrator behaviour : I can see in Apache
log files Sogo-Integrator access to updates.php file at each
thunderbird starts.
But, Integrator doesn't fetch xpi files. How to force Integrator to
fetch modified xpi files? Should I change   each time I patch my sogo-integrator xpi
files?

Thank you,

Matthieu
-- 

  
  

  

Matthieu ROGER
  
  


  
  
23 rue de
  la Fraternité - 95460 Ezanville - France
Tél. : +33 (1) 30 11 81 50 - Fax : +33 (1) 30
  11 81 49
www.lanetcie.com


  
  


  

  
  

  



[SOGo] SSO using vulture

2011-06-08 Thread Sébastien Posé

Hi,

I'm trying to use sogo throw vulture. I would like vulture authenticates 
my users by sending their login and password to the sogo's connection 
page (SSO feature).


I'm able to authenticate users but they are redirected to /SOGo/connect 
and got:

{"grace": -1, "expire": -1}

If I remove /connect and refresh, I'm redirected to 
/SOGo/so/sebastien.pose/Mail/view and everything is ok.


Has anyone encountered a similar problem?

Thanks.
--
Sébastien Posé
Division des Services Informatiques
Rectorat de la Réunion
--
users@sogo.nu
https://inverse.ca/sogo/lists


Re: [SOGo] view filter: all future events, recurring events dont show up

2011-06-08 Thread Francis Lachapelle
Hi Rob

On 2011-06-08, at 3:38 AM,  
 wrote:

> Is this a "feature" or a bug? I have the latest nightly build installed on
> centos with postgres and LDAP for authentication. I am using the Web interface
> 
> I create an event with a custom recurring period, ie every 3 months on every
> third Wednesday for 3 appointments, several other users are added as invitees.
> I then tweak the second and third events times and days slightly by setting
> them at slightly different times or dates.
> 
> now, when I set the view drop down box to all future events, the second and
> third events don't show up in the list at the top of the screen. but they do 
> if
> you set view to selected day and select the day where the event is on.
> 
> its as if the future events filter doesn't go through the recurring parts of
> the data for the events. The reason I ask if its a feature is because (being a
> software developer) it almost makes a strange kind of sense to me to only show
> the initial version in the top list, and not the recurring sections, mind you
> the more I think about it the more I think its just a bug.

It's a design choice. You'll also notice that the list view mode is only saved 
in the user's preferences if it's not "All future events".

Eventually, we could at least show recurrent events that have a finite duration.


Francis

--
flachape...@inverse.ca :: +1.514.755.3640 :: http://www.inverse.ca
Inverse :: Leaders behind SOGo (http://sogo.nu) and PacketFence 
(http://packetfence.org)

-- 
users@sogo.nu
https://inverse.ca/sogo/lists

[SOGo] view filter: all future events, recurring events dont show up

2011-06-08 Thread robert_robinson
Hi,

Is this a "feature" or a bug? I have the latest nightly build installed on
centos with postgres and LDAP for authentication. I am using the Web interface

I create an event with a custom recurring period, ie every 3 months on every
third Wednesday for 3 appointments, several other users are added as invitees.
I then tweak the second and third events times and days slightly by setting
them at slightly different times or dates.

now, when I set the view drop down box to all future events, the second and
third events don't show up in the list at the top of the screen. but they do if
you set view to selected day and select the day where the event is on.

its as if the future events filter doesn't go through the recurring parts of
the data for the events. The reason I ask if its a feature is because (being a
software developer) it almost makes a strange kind of sense to me to only show
the initial version in the top list, and not the recurring sections, mind you
the more I think about it the more I think its just a bug.

anyone else had this problem?

Rob
-- 
users@sogo.nu
https://inverse.ca/sogo/lists