Using a SSO in eZ Publish - community.ez.no

Wednesday 23 December 2009 2:23:38 am - 6 replies

Introduction

Sometimes, during a web application development, you need to interface with your client's software(s) and/or websites in order to keep a common and coherent session within its applicative environment. To do this, it is often useful to use a special tool : SSO (Single Sign On). This article illustrates one way of integrating an eZ Publish based web application into an existing SSO architecture

6 replies

Author	Message
SEBBANE Alexandre	Saturday 26 December 2009 11:18:01 am I have just publish a little example for sso_handler : bpce_acces. It consists of an SSO Handeler based on client IP. Paris, France
Jianjun Hu	Saturday 26 December 2009 3:28:39 pm I'm looking forward your article. OnlyBlue ☆．．·°∴°．☆°°．☆°． °∴ °☆ ．·enjoy star° ．·★°∴° ∴°．°★ ．·° 　ミ☆°∴°．★☆° ∴·° °．☆° ．·∴°　 Is it a pleasure after all to practice in due time what one has learnt?
Nicolas OTTAVI	Tuesday 06 July 2010 1:40:15 am Hi, Thanks for this tutorial, I have implemented a SSO and it works fine. But it seems the SSOHandler is called everytime a page is loaded. I am wondering if I am doing something wrong, as I think the call is need only when the current user is Anonymous. Is there a way to stop the SSOHandler call when a user is already logged in ? Or should I put this "logic" in the SSOHandler::handleSSOLogin() method? Thanks for the answer. Nico O
Jérôme Vieilledent	Tuesday 06 July 2010 3:15:18 am Hi Nicolas SSOHandler will be called every time a page is loaded if your user is not logged in, as SSO is handled in eZUser::instance() method. Once your user is logged in, it won't be called any more. So maybe you should add some logic in your SSOHandler::handleSSOLogin() in order not to call your login webservice (or other SSO stuffs) if you are not logging in.
Gaetano Giunta	Tuesday 06 July 2010 8:26:14 am Otoh if you want also SingleSignOff, your code should be called on every page, for both logged-in and anon users. eZ Publish does not currently support that afair, but it is a requirement seldom see in real life... Principal Consultant International Business Member of the Community Project Board
Hamadou BABA	Wednesday 09 February 2011 9:30:14 am Hi Nicolas, I could learn from this forum that you're successful in implementing SSO. That isn't my case. I would greatly appreciate if you can post me the code you implemented. I used the SPNEGO projet but I'm still unable to get it working as designed for. Thanking you in advance.

You must be logged in to post messages in this topic!

eZ debug

Timing:	Jan 28 2025 14:01:05
Script start
Timing:	Jan 28 2025 14:01:05
Module start 'layout'
Timing:	Jan 28 2025 14:01:05
Module start 'content'
Timing:	Jan 28 2025 14:01:05
Module end 'content'
Timing:	Jan 28 2025 14:01:05
Script end

Main resources:

Total runtime	0.0345 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0052	595.1797	151.2109
Module start 'layout'	0.0052	0.0022	746.3906	36.6484
Module start 'content'	0.0074	0.0252	783.0391	102.7266
Module end 'content'	0.0326	0.0018	885.7656	37.9922
Script end	0.0344		923.7578

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0023	6.6001	14	0.0002
Check MTime	0.0011	3.2083	14	0.0001
Mysql Total
Database connection	0.0009	2.5634	1	0.0009
Mysqli_queries	0.0023	6.6942	3	0.0008
Looping result	0.0000	0.0374	1	0.0000
Template Total	0.0013	3.7	1	0.0013
Template load	0.0010	2.9724	1	0.0010
Template processing	0.0002	0.6768	1	0.0002
Override
Cache load	0.0007	1.9419	1	0.0007
General
dbfile	0.0133	38.5542	8	0.0017
String conversion	0.0000	0.0173	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs