unity-idm-discuss

[Unity-idm-discuss] Relative SAML SP metadata paths

[D B. <ba...@aw...>]

Hi,

I just ran into the fact that between version 2.5 and 3.2 the
acceptedSPMetadataSource.*.url setting changed behaviour when using
file:// urls. It now interprets these URLs relative to the unity
directory, so what was formerly
unity.saml.acceptedSPMetadataSource.sp.url=file:///etc/unity-idm/metadata.xml
became
unity.saml.acceptedSPMetadataSource.sp.url=file:///metadata.xml

Could you mention that in the docs in the description for
unity.saml.acceptedSPMetadataSource .*.url ?

It's really not obvious from the error message in the logs:

ERROR unity.server.URIAccessServiceImpl: Can not read uri:
file:///etc/unity-idm/metadata.xml
pl.edu.icm.unity.exceptions.EngineException: Can not read file from uri:
file:///etc/unity-idm/metadata.xml
        at
pl.edu.icm.unity.engine.files.URIAccessServiceImpl.readUriInternal(URIAccessServiceImpl.java:148)
~[unity-server-engine-3.2.0.jar:?]
        at
pl.edu.icm.unity.engine.files.URIAccessServiceImpl.readURI(URIAccessServiceImpl.java:71)
~[unity-server-engine-3.2.0.jar:?]

Cheers,
D

Re: [Unity-idm-discuss] Relative SAML SP metadata paths

[Krzysztof B. <kb...@un...>]

Hi,

W dniu 05.03.2020 o 15:23, D Baum pisze:
> Hi,
>
> I just ran into the fact that between version 2.5 and 3.2 the
> acceptedSPMetadataSource.*.url setting changed behaviour when using
> file:// urls. It now interprets these URLs relative to the unity
> directory, so what was formerly
> unity.saml.acceptedSPMetadataSource.sp.url=file:///etc/unity-idm/metadata.xml
> became
> unity.saml.acceptedSPMetadataSource.sp.url=file:///metadata.xml
>
> Could you mention that in the docs in the description for
> unity.saml.acceptedSPMetadataSource .*.url ?
>
> It's really not obvious from the error message in the logs:
>
> ERROR unity.server.URIAccessServiceImpl: Can not read uri:

Sure, we can improve docs.

One question: both versions of you installation were RPM? Or one was RPM 
and another tar.gz?

Best
Krzysztof

Re: [Unity-idm-discuss] Relative SAML SP metadata paths

[D B. <ba...@aw...>]

Hi,

if I remember correctly the 2.5 installation was rpm, the 3.2 is tar.gz
(now).

D

On 06/03/2020 09:32, Krzysztof Benedyczak wrote:
> Hi,
> 
> W dniu 05.03.2020 o 15:23, D Baum pisze:
>> Hi,
>>
>> I just ran into the fact that between version 2.5 and 3.2 the
>> acceptedSPMetadataSource.*.url setting changed behaviour when using
>> file:// urls. It now interprets these URLs relative to the unity
>> directory, so what was formerly
>> unity.saml.acceptedSPMetadataSource.sp.url=file:///etc/unity-idm/metadata.xml
>>
>> became
>> unity.saml.acceptedSPMetadataSource.sp.url=file:///metadata.xml
>>
>> Could you mention that in the docs in the description for
>> unity.saml.acceptedSPMetadataSource .*.url ?
>>
>> It's really not obvious from the error message in the logs:
>>
>> ERROR unity.server.URIAccessServiceImpl: Can not read uri:
> 
> Sure, we can improve docs.
> 
> One question: both versions of you installation were RPM? Or one was RPM
> and another tar.gz?
> 
> Best
> Krzysztof
> 

Re: [Unity-idm-discuss] Relative SAML SP metadata paths

[Krzysztof B. <kb...@un...>]

W dniu 06.03.2020 o 10:43, D Baum pisze:
> Hi,
>
> if I remember correctly the 2.5 installation was rpm, the 3.2 is tar.gz
> (now).

So I think this is root of confusion. There was not change between 2.5 
and 3.2 up to my knowledge. But the root for RPM/deb is '/', for tar.gz 
it is install dir. Most of the time this is irrelevant as base config 
files have variables with root dir/conf dir etc., but this not used by 
subsystems-defined configs (like saml endpoint) which are processed by 
those subsystems.

K