<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
I've another odd one. <br>
<br>
Working with a vendor to configure their SP. They only
support/certify the following IdP's (Okta, Azure Active Directory,
Ping Federate, F5 and onelogin) and not Shibboleth.<br>
<br>
We have a non-production Shibboleth IdP server and I was able to get
a working configuration to login via this non-production Shibboleth
IdP and a test instance of their application, using a "IdP
Initiated" model.<br>
<br>
On our non-production Shibboleth IdP it has a <b>https://</b> url
style entityID value that we made up when we build this server. On
our production Shibboleth IdP, it has a <b>urn:mace:incommon:</b>
style entityID value.<br>
<br>
Needless to say this vendor is not a InCommon member.<br>
<br>
I do not even know how to answer their questions as to why our
production Shibboleth IdP has a urn: vs a https: style entityID
value. I have a whole bunch of other questions running in my mind I
do not even know how to ask.<br>
<br>
Sorry,<br>
Don<br>
<pre class="moz-signature" cols="72">--
D o n a l d L o h r
I n f o r m a t i o n S y s t e m s
J a m e s M a d i s o n U n i v e r s i t y
5 4 0 . 5 6 8 . 3 7 3 0
</pre>
</body>
</html>