You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: xt/testapp/README.md
+24-5Lines changed: 24 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ Access http://localhost:3000
33
33
34
34
### Run lighttpd to proxy https to the Saml2Test application
35
35
36
-
Many SAML2 Identity Providers will not allow the application (Service Provider) URL to be http and force you to specify https to use SAML2. lighttpd is used to listen on port 443 and use https protocol so that the Identity Provider can redirect or POST to a https site. lighttpd then proxies that communication to the Dancer application listening on port 3000.
36
+
Many SAML2 Identity Providers will not allow the application (Service Provider) URL to be http and forces you to specify https to use SAML2. lighttpd is used to listen on port 443 and use https protocol so that the Identity Provider can redirect or POST to a https site. lighttpd then proxies that communication to the Dancer application listening on port 3000.
37
37
38
38
1. cd xt/testapp
39
39
2. sudo lighttpd -D -f lighttpd.conf
@@ -42,11 +42,30 @@ Note that the command requires sudo to allow it to use the default https port of
42
42
43
43
TODO: maybe change it to use 8443
44
44
45
-
### Create your metadata.xml file
45
+
### Configure the testapp to connect to the Identity Provider
46
46
47
-
Download the metadata for you configured application from your Identity Provider and save it to:
47
+
The testapp now supports a simplified automatic configuration for testing against multiple Identity Providers (IdPs).
48
48
49
-
xt/testapp/metadata.xml
49
+
1. Simply create a directory in xt/testapp/IdPs for the name of the IdP (eg. google)
50
+
2. Download the metadata from your IdP and save it as IdPs/google/metadata.xml
51
+
3. Download the cacert.pem from the IdP and save it as IdPs/google/cacert.pem
52
+
4. Optionally create IdPs/google/config.yml for custom settings for the IdP (if the a custom config.yml does not exist it will refresh the settings from the default config.yml.
53
+
54
+
The index page will automatically list each configured Identity Provider as a link to initiate login against that IdP.
55
+
56
+
Your directory structure should look like:
57
+
58
+
IdPs/
59
+
auth0/
60
+
cacert.pem
61
+
metadata.yml
62
+
azure/
63
+
cacert.pem
64
+
config.yml (optional)
65
+
metadata.yml
66
+
google/
67
+
cacert.pem
68
+
metadata.yml
50
69
51
70
### Run lighttpd to deliver metadata.xml
52
71
@@ -55,7 +74,7 @@ Net::SAML2 requires access to a URL containing the metadata. The simplest metho
55
74
1. cd xt/testapp
56
75
2. lighttpd -D -f lighttpd-metadata.conf
57
76
58
-
The metadata has been configured to be available at: http://localhost:8880/metadata.xml.
77
+
The metadata has been configured to be available at: http://localhost:8880/metadata.xml. The simplified IdP configuration will automatically access the metadata.xml at http://localhost:8880/IdPs/google/metadata.xml (if you followed the instructions above and created the google directory in xt/testapp/IdPs)
59
78
60
79
Note that the configuration attempts to only deliver a file named metadata.xml from the xt/testapp directory. There are no guarantees - this is a test application so verify your own security.
0 commit comments