* Francisco Almeida <
fral...@gmail.com> [2016-02-23 02:01]:
> In my case I have a 'saml:SP' that I would like to extend. Should I create
> my own custom module? What is the best practice for this issue?
The example code from the documentation goes into the PHP code from
where you initiate sessions using SimpleSAMLphp's PHP API.
It's not something done in SimpleSAMLphp's configuration (though since
that's just PHP code as well that could probably be done, somewhere).
How are you triggering SSO now, if not in your own PHP code?
Are you using some application (e.g. Drupal or Wordpress) plus some
module that integrates that with SimpleSAMLphp's API?
If so, that module/extension has the code where SSO is initiated and
that's where you'd need to add the code from the documentation,
adapting it as needed (authsouce name, actual extension data).
So why not start with the simple case by creating an empty file to
your web server hosting your SimpleSAMLphp SP, then add the required
PHP code to that page as per the SimpleSAMLphp documentation Jaime
pointed you to. Then you'll have a handful of lines of code that will
trigger SSO (and SLO, if you add that, too) and you can test the
effect of your added extensions. Only once that all works as desired
look into how to get that code into the right place for your current
application.
-peter