You can subscribe to this list here.
2014 |
Jan
(3) |
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(2) |
Aug
(2) |
Sep
|
Oct
(3) |
Nov
|
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2015 |
Jan
(20) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
(15) |
Jul
(1) |
Aug
(7) |
Sep
(13) |
Oct
(2) |
Nov
(10) |
Dec
(1) |
2016 |
Jan
|
Feb
(2) |
Mar
|
Apr
(2) |
May
(1) |
Jun
|
Jul
(1) |
Aug
(2) |
Sep
(11) |
Oct
(7) |
Nov
(6) |
Dec
(11) |
2017 |
Jan
(10) |
Feb
(5) |
Mar
(27) |
Apr
(34) |
May
(25) |
Jun
(14) |
Jul
(7) |
Aug
(17) |
Sep
(11) |
Oct
(6) |
Nov
(14) |
Dec
(10) |
2018 |
Jan
(8) |
Feb
(19) |
Mar
(40) |
Apr
(9) |
May
(16) |
Jun
(23) |
Jul
(31) |
Aug
(7) |
Sep
(9) |
Oct
(6) |
Nov
(14) |
Dec
(19) |
2019 |
Jan
(4) |
Feb
(6) |
Mar
(1) |
Apr
(2) |
May
(6) |
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(19) |
Dec
(14) |
2020 |
Jan
(10) |
Feb
(24) |
Mar
(49) |
Apr
(26) |
May
(12) |
Jun
(4) |
Jul
(13) |
Aug
(32) |
Sep
(13) |
Oct
(10) |
Nov
(4) |
Dec
(16) |
2021 |
Jan
(2) |
Feb
(8) |
Mar
(15) |
Apr
(19) |
May
(5) |
Jun
(13) |
Jul
(6) |
Aug
(38) |
Sep
(11) |
Oct
(18) |
Nov
(11) |
Dec
(13) |
2022 |
Jan
(10) |
Feb
(21) |
Mar
(28) |
Apr
(3) |
May
(7) |
Jun
(9) |
Jul
(14) |
Aug
(13) |
Sep
(8) |
Oct
(29) |
Nov
(1) |
Dec
(21) |
2023 |
Jan
(19) |
Feb
(9) |
Mar
|
Apr
(10) |
May
(7) |
Jun
(10) |
Jul
(14) |
Aug
(17) |
Sep
(1) |
Oct
(9) |
Nov
(5) |
Dec
(14) |
2024 |
Jan
(12) |
Feb
(2) |
Mar
(8) |
Apr
(1) |
May
(6) |
Jun
(6) |
Jul
(24) |
Aug
(15) |
Sep
(1) |
Oct
(6) |
Nov
(20) |
Dec
(14) |
2025 |
Jan
(12) |
Feb
(2) |
Mar
(10) |
Apr
(11) |
May
(13) |
Jun
(1) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Krzysztof B. <kb...@un...> - 2020-04-02 13:39:41
|
W dniu 02.04.2020 o 15:30, D Baum pisze: > Yes, that's it, thanks a lot! > > What's with this default setting? This sounds unusual. Is the normal > unity usecase for internal authentication where all clients have a cert > installed? > well, if you don't have a personal certificate installed in your browser's keystore, what is true for 99+% users then you won't be bugged by the browser (with exception of Safari AFAIR). So that's not that bad in general. But true we can think about changing the default, it used to be more needed in the past. Especially as TLS authN is passing away with FIDO2/WebAuthn. |
From: D B. <ba...@aw...> - 2020-04-02 13:30:26
|
Yes, that's it, thanks a lot! What's with this default setting? This sounds unusual. Is the normal unity usecase for internal authentication where all clients have a cert installed? Cheers, D On 02/04/2020 13:39, Sander Apweiler wrote: > Hi D, > did you set unityServer.core.httpServer.wantClientAuthn to false? By > default it is true and requests a client certificate during the > handshake. > > Cheers, > Sander > > > On Thu, 2020-04-02 at 13:36 +0200, D Baum wrote: >> Hi, >> >> I've deactivated the 'cert' credential where I could find it in the >> config and GUI but unity keeps asking my users for a client >> certificate >> (on login). >> It happens only in Safari and Chrome, not in Firefox, apparently. >> >> Any tips on how to resolve this? >> >> Cheers, >> D >> >> >> _______________________________________________ >> Unity-idm-discuss mailing list >> Uni...@li... >> https://lists.sourceforge.net/lists/listinfo/unity-idm-discuss |
From: Sander A. <sa....@fz...> - 2020-04-02 11:39:59
|
Hi D, did you set unityServer.core.httpServer.wantClientAuthn to false? By default it is true and requests a client certificate during the handshake. Cheers, Sander On Thu, 2020-04-02 at 13:36 +0200, D Baum wrote: > Hi, > > I've deactivated the 'cert' credential where I could find it in the > config and GUI but unity keeps asking my users for a client > certificate > (on login). > It happens only in Safari and Chrome, not in Firefox, apparently. > > Any tips on how to resolve this? > > Cheers, > D > > > _______________________________________________ > Unity-idm-discuss mailing list > Uni...@li... > https://lists.sourceforge.net/lists/listinfo/unity-idm-discuss -- Federated Systems and Data Juelich Supercomputing Centre phone: +49 2461 61 8847 fax: +49 2461 61 6656 email: sa....@fz... ---------------------------------------------------------------------- ----------------------------------------------------------------------- Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Volker Rieke Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt ----------------------------------------------------------------------- ----------------------------------------------------------------------- |
From: D B. <ba...@aw...> - 2020-04-02 11:36:40
|
Hi, I've deactivated the 'cert' credential where I could find it in the config and GUI but unity keeps asking my users for a client certificate (on login). It happens only in Safari and Chrome, not in Firefox, apparently. Any tips on how to resolve this? Cheers, D |
From: Krzysztof B. <kb...@un...> - 2020-04-02 10:30:39
|
W dniu 01.04.2020 o 10:57, Sander Apweiler pisze: > Hi Krzysztof, > > at the moment we are using different versions of unity: 2.8.2, 3.2.0 > Java version: openjdk version "1.8.0_161" > OK, so I after some checking (was not so easy as our instances are mostly behind proxies) it seems that it depends :-) On quite a few things like JVM version, settings, ciphersuites etc. Jetty officially has documented that TLS 1.0 and 1.1 are disabled by default but it seems not to be the case always in practice. So to simplify the landscape, in the version 3.2.2 there will be a new option allowing to disable specific protocol versions allowed by the Unity's HTTPS server, regardless of the JVM settings. What is more in 3.3.0 the TLS 1.1 and 1.0 will be disabled *by default*. Cheers, Krzysztof |
From: Sander A. <sa....@fz...> - 2020-04-01 08:57:57
|
Hi Krzysztof, at the moment we are using different versions of unity: 2.8.2, 3.2.0 Java version: openjdk version "1.8.0_161" Cheers, Sander On Wed, 2020-04-01 at 10:53 +0200, Krzysztof Benedyczak wrote: > Hi Sander, > > W dniu 01.04.2020 o 09:57, Sander Apweiler pisze: > > Hi Krzysztof, > > > > is it possible to disable specific TLS versions (1.0 and 1.1)? I > > found > > only the unityServer.core.httpServer.disabledCipherSuites parameter > > we > > already use for a list of outdated cipher suits. > > > Which Unity version and which Java version you use? > > KB > > -- Federated Systems and Data Juelich Supercomputing Centre phone: +49 2461 61 8847 fax: +49 2461 61 6656 email: sa....@fz... ---------------------------------------------------------------------- ----------------------------------------------------------------------- Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Volker Rieke Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt ----------------------------------------------------------------------- ----------------------------------------------------------------------- |
From: Krzysztof B. <kb...@un...> - 2020-04-01 08:53:20
|
Hi Sander, W dniu 01.04.2020 o 09:57, Sander Apweiler pisze: > Hi Krzysztof, > > is it possible to disable specific TLS versions (1.0 and 1.1)? I found > only the unityServer.core.httpServer.disabledCipherSuites parameter we > already use for a list of outdated cipher suits. > Which Unity version and which Java version you use? KB |
From: Marcus H. <ha...@ki...> - 2020-04-01 08:31:48
|
Are you referring to the "B" from here: https://www.ssllabs.com/ssltest/analyze.html?d=login.helmholtz-data-federation.de M. On 04/01/20 09:57, Sander Apweiler wrote: > Hi Krzysztof, > > is it possible to disable specific TLS versions (1.0 and 1.1)? I found > only the unityServer.core.httpServer.disabledCipherSuites parameter we > already use for a list of outdated cipher suits. > > Cheers, > Sander > -- > Federated Systems and Data > Juelich Supercomputing Centre > > phone: +49 2461 61 8847 > fax: +49 2461 61 6656 > email: sa....@fz... > > ---------------------------------------------------------------------- > ----------------------------------------------------------------------- > Forschungszentrum Juelich GmbH > 52425 Juelich > Sitz der Gesellschaft: Juelich > Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 > Vorsitzender des Aufsichtsrats: MinDir Volker Rieke > Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), > Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt > ----------------------------------------------------------------------- > ----------------------------------------------------------------------- > _______________________________________________ > Unity-idm-discuss mailing list > Uni...@li... > https://lists.sourceforge.net/lists/listinfo/unity-idm-discuss -- Marcus. |
From: Sander A. <sa....@fz...> - 2020-04-01 07:58:25
|
Hi Krzysztof, is it possible to disable specific TLS versions (1.0 and 1.1)? I found only the unityServer.core.httpServer.disabledCipherSuites parameter we already use for a list of outdated cipher suits. Cheers, Sander -- Federated Systems and Data Juelich Supercomputing Centre phone: +49 2461 61 8847 fax: +49 2461 61 6656 email: sa....@fz... ---------------------------------------------------------------------- ----------------------------------------------------------------------- Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Volker Rieke Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt ----------------------------------------------------------------------- ----------------------------------------------------------------------- |
From: Krzysztof B. <kb...@un...> - 2020-03-28 22:16:32
|
Hi Sander, W dniu 14.03.2020 o 10:30, Krzysztof Benedyczak pisze: > Hi Sander, > > W dniu 11.03.2020 o 12:05, Sander Apweiler pisze: >> Hi Krzysztof, >> >> this is still an issue for us and users asked for some updates. How is >> your plan with the RO-user? Good news, I was completely wrong here. When I tried to check how difficult it is to implement, I've discovered that... this feature is available. Just set the "Anonymous user" role to your oauth client. It is exactly what you need: a fully read only user, who can not modify even its own credential. We should change the name of this role to "Read only user" eventually... Cheers, Krzysztof |
From: Sander A. <sa....@fz...> - 2020-03-26 08:20:55
|
Hi Krzysztof, the issue is solved. After a hint from Tim I found the problem. Python entered the values as string and not as an array. Now it works. Cheers, Sander On Wed, 2020-03-25 at 17:39 +0100, Sander Apweiler wrote: > Hi Krzysztof, > > I try to set a multivalue attribute using the rest API, but every > time > the content is stored in one value. The attribute is configured as > multivalue attribute. > > First I tried to add the value element multiple times within the > values > array. This was my payload: > {\'values\': [\'{"value":" > http://localhost:4242","tags":[]},{"value":"http://localhost:8080","tags":[]},{"value":"http://localhost:43985","tags":[]}\' > ], \'name\': \'sys:oauth:allowedReturnURI\', \'groupPath\': \'/\'} > which lead to the value: {"value":" > http://localhost:4242","tags":[]},{"value":"http://localhost:8080","tags":[]},{"value":"http://localhost:43985","tags":[] > } > > So I removed the parts from the request which are wrong in the > attribute and I tried with this payload: > {\'values\': [\'" > http://localhost:4242","http://localhost:8080","http://localhost:43985"\' > ], \'name\': \'sys:oauth:allowedReturnURI\', \'groupPath\': \'/\'} > which lead to the value " > http://localhost:4242","http://localhost:8080","http://localhost:43985 > " > > After having a look in the Get response, I tried with this payload: > {\'values\': [\'" > http://localhost:4242",\\n"http://localhost:8080",\\n"http://localhost:43985"\' > ], \'name\': \'sys:oauth:allowedReturnURI\', \'groupPath\': \'/\'} > which lead to the value: > "http://localhost:4242", > "http://localhost:8080", > "http://localhost:43985" > > I tried calling the API multiple time, but this changes only the > value. > This is fine, because it should be possible to update the existing > value. > > Can you give me a hint how to set multivalues using the rest API? > > Best regards, > Sander -- Federated Systems and Data Juelich Supercomputing Centre phone: +49 2461 61 8847 fax: +49 2461 61 6656 email: sa....@fz... ---------------------------------------------------------------------- ----------------------------------------------------------------------- Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Volker Rieke Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt ----------------------------------------------------------------------- ----------------------------------------------------------------------- |
From: Sander A. <sa....@fz...> - 2020-03-25 16:39:23
|
Hi Krzysztof, I try to set a multivalue attribute using the rest API, but every time the content is stored in one value. The attribute is configured as multivalue attribute. First I tried to add the value element multiple times within the values array. This was my payload: {\'values\': [\'{"value":"http://localhost:4242","tags":[]},{"value":"http://localhost:8080","tags":[]},{"value":"http://localhost:43985","tags":[]}\'], \'name\': \'sys:oauth:allowedReturnURI\', \'groupPath\': \'/\'} which lead to the value: {"value":"http://localhost:4242","tags":[]},{"value":"http://localhost:8080","tags":[]},{"value":"http://localhost:43985","tags":[]} So I removed the parts from the request which are wrong in the attribute and I tried with this payload: {\'values\': [\'"http://localhost:4242","http://localhost:8080","http://localhost:43985"\'], \'name\': \'sys:oauth:allowedReturnURI\', \'groupPath\': \'/\'} which lead to the value "http://localhost:4242","http://localhost:8080","http://localhost:43985" After having a look in the Get response, I tried with this payload: {\'values\': [\'"http://localhost:4242",\\n"http://localhost:8080",\\n"http://localhost:43985"\'], \'name\': \'sys:oauth:allowedReturnURI\', \'groupPath\': \'/\'} which lead to the value: "http://localhost:4242", "http://localhost:8080", "http://localhost:43985" I tried calling the API multiple time, but this changes only the value. This is fine, because it should be possible to update the existing value. Can you give me a hint how to set multivalues using the rest API? Best regards, Sander -- Federated Systems and Data Juelich Supercomputing Centre phone: +49 2461 61 8847 fax: +49 2461 61 6656 email: sa....@fz... ---------------------------------------------------------------------- ----------------------------------------------------------------------- Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Volker Rieke Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt ----------------------------------------------------------------------- ----------------------------------------------------------------------- |
From: Krzysztof B. <kb...@un...> - 2020-03-25 09:43:17
|
Hi, W dniu 24.03.2020 o 17:08, D Baum pisze: > Hi! > > just found that on my unity instance I can register as separate entities > with userNames "dbaum", "DBaum", "DbAuM", etc. > > In itself, I find this a little confusing for the moderators/admins > (remembering that DBaum and dbaum can be different people). > > However, my unity clients don't all take capitalisation into account > when retrieving user data (see, e.g. > https://stackoverflow.com/questions/44821863/spring-boot-security-consider-case-insensitive-username-check-for-login/) > > I realise that this could be exploited to hijack a user's account if you > know the username, by registering the same username with different > capitalisation in unity and then logging into the client. > > Now, I've fixed this on the client side for my setup (where it should be > fixed). But can I ask that you consider adding a feature where users are > prevented from registering entities with usernames that differ from > existing ones only in capitalisation? Yes, makes sense. We have this supported since quite a long time for email identities (I guess more popular nowadays) but such feature can be also added for usernames. Cheers, Krzysztof |
From: Krzysztof B. <kb...@un...> - 2020-03-25 09:14:19
|
W dniu 24.03.2020 o 17:08, D Baum pisze: > Hi! > > just found that on my unity instance I can register as separate entities > with userNames "dbaum", "DBaum", "DbAuM", etc. > > In itself, I find this a little confusing for the moderators/admins > (remembering that DBaum and dbaum can be different people). > > However, my unity clients don't all take capitalisation into account > when retrieving user data (see, e.g. > https://stackoverflow.com/questions/44821863/spring-boot-security-consider-case-insensitive-username-check-for-login/) > > I realise that this could be exploited to hijack a user's account if you > know the username, by registering the same username with different > capitalisation in unity and then logging into the client. > > Now, I've fixed this on the client side for my setup (where it should be > fixed). But can I ask that you consider adding a feature where users are > prevented from registering entities with usernames that differ from > existing ones only in capitalisation? Just to clarify: we won't be able to just change the matching, what is technically trivial but may break many things: PAM based authN for instance or existing databases where there are already multiple usernames differing only with case. So this will be either a new identity type or an config option for username identity type. KB |
From: D B. <ba...@aw...> - 2020-03-24 16:09:06
|
Hi! just found that on my unity instance I can register as separate entities with userNames "dbaum", "DBaum", "DbAuM", etc. In itself, I find this a little confusing for the moderators/admins (remembering that DBaum and dbaum can be different people). However, my unity clients don't all take capitalisation into account when retrieving user data (see, e.g. https://stackoverflow.com/questions/44821863/spring-boot-security-consider-case-insensitive-username-check-for-login/) I realise that this could be exploited to hijack a user's account if you know the username, by registering the same username with different capitalisation in unity and then logging into the client. Now, I've fixed this on the client side for my setup (where it should be fixed). But can I ask that you consider adding a feature where users are prevented from registering entities with usernames that differ from existing ones only in capitalisation? Cheers D |
From: D B. <ba...@aw...> - 2020-03-24 10:17:46
|
Hi, thanks again! A condition based on `requester` seems to be what I'm looking for :-) D On 20/03/2020 19:20, Sander Apweiler wrote: > Hi, > > entityId seems not to be in the output profile, see [1]. We did it with > requester and added the server manually with testing if it was the URL > or the entityID. But we did not use entityID as special parameter. > > Cheers, > Sander > > [1]: https://www.unity-idm.eu/documentation/unity-3.2.1/manual.html#_output_translation > > On Fri, 2020-03-20 at 15:51 +0100, D Baum wrote: >> Hi, >> >> On 20/03/2020 07:13, Sander Apweiler wrote: >>> 2. Same as above but change the condition from true to some >>> expresion >>> with something like "requester=serviceA". I can't remember if we >>> had >>> used only the server name or entityID in this place. >> >> Thanks, that's the sort of thing I was looking for! >> >> For testing, I tried creating a rule with a condition based on >> entityId >> and another one just adding the entityId as an attribute: >> >> createAttribute|attributeName: entityId|expression: >> entityId|mandatory: >> false|attributeDisplayName: |attributeDescription: |type: >> >> In the logs, I'm getting >> org.mvel2.PropertyAccessException: [Error: could not access: >> entityId; >> in class: java.util.HashMap] >> [Near : {... entityId ....}] >> ^ >> [Line: 1, Column: 1] >> >> According to >> https://www.unity-idm.eu/documentation/unity-3.2.1/manual.html#attributes >> entityId should be available similar to attr. >> >> What am I doing wrong? >> >> Cheers, >> D >> >> >> _______________________________________________ >> Unity-idm-discuss mailing list >> Uni...@li... >> https://lists.sourceforge.net/lists/listinfo/unity-idm-discuss |
From: Sander A. <sa....@fz...> - 2020-03-20 18:21:14
|
Hi, entityId seems not to be in the output profile, see [1]. We did it with requester and added the server manually with testing if it was the URL or the entityID. But we did not use entityID as special parameter. Cheers, Sander [1]: https://www.unity-idm.eu/documentation/unity-3.2.1/manual.html#_output_translation On Fri, 2020-03-20 at 15:51 +0100, D Baum wrote: > Hi, > > On 20/03/2020 07:13, Sander Apweiler wrote: > > 2. Same as above but change the condition from true to some > > expresion > > with something like "requester=serviceA". I can't remember if we > > had > > used only the server name or entityID in this place. > > Thanks, that's the sort of thing I was looking for! > > For testing, I tried creating a rule with a condition based on > entityId > and another one just adding the entityId as an attribute: > > createAttribute|attributeName: entityId|expression: > entityId|mandatory: > false|attributeDisplayName: |attributeDescription: |type: > > In the logs, I'm getting > org.mvel2.PropertyAccessException: [Error: could not access: > entityId; > in class: java.util.HashMap] > [Near : {... entityId ....}] > ^ > [Line: 1, Column: 1] > > According to > https://www.unity-idm.eu/documentation/unity-3.2.1/manual.html#attributes > entityId should be available similar to attr. > > What am I doing wrong? > > Cheers, > D > > > _______________________________________________ > Unity-idm-discuss mailing list > Uni...@li... > https://lists.sourceforge.net/lists/listinfo/unity-idm-discuss -- Federated Systems and Data Juelich Supercomputing Centre phone: +49 2461 61 8847 fax: +49 2461 61 6656 email: sa....@fz... ---------------------------------------------------------------------- ----------------------------------------------------------------------- Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Volker Rieke Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt ----------------------------------------------------------------------- ----------------------------------------------------------------------- |
From: D B. <ba...@aw...> - 2020-03-20 14:51:28
|
Hi, On 20/03/2020 07:13, Sander Apweiler wrote: > 2. Same as above but change the condition from true to some expresion > with something like "requester=serviceA". I can't remember if we had > used only the server name or entityID in this place. Thanks, that's the sort of thing I was looking for! For testing, I tried creating a rule with a condition based on entityId and another one just adding the entityId as an attribute: createAttribute|attributeName: entityId|expression: entityId|mandatory: false|attributeDisplayName: |attributeDescription: |type: In the logs, I'm getting org.mvel2.PropertyAccessException: [Error: could not access: entityId; in class: java.util.HashMap] [Near : {... entityId ....}] ^ [Line: 1, Column: 1] According to https://www.unity-idm.eu/documentation/unity-3.2.1/manual.html#attributes entityId should be available similar to attr. What am I doing wrong? Cheers, D |
From: Sander A. <sa....@fz...> - 2020-03-20 06:13:40
|
Hi, you have different ways to do it. 1. Just create two rules one with attributeName=urn.... and one with attributeName=username. In this case the attribute is released every time in both formats. 2. Same as above but change the condition from true to some expresion with something like "requester=serviceA". I can't remember if we had used only the server name or entityID in this place. 3. Most complex and mostly not wanted: Create multiple endpoints to the services. In this case you can create dedicated translation profiles for the service. Cheers, Sander On Thu, 2020-03-19 at 17:59 +0100, D Baum wrote: > Hi, > > is it possible to serve different entity attributes to different SPs > with unity? > Say I want to serve the username as > "urn:mace:dir:attribute-def:cn" to one SP but as "username" to > another. > Is that feasible? > > Cheers, > D > > > _______________________________________________ > Unity-idm-discuss mailing list > Uni...@li... > https://lists.sourceforge.net/lists/listinfo/unity-idm-discuss -- Federated Systems and Data Juelich Supercomputing Centre phone: +49 2461 61 8847 fax: +49 2461 61 6656 email: sa....@fz... ---------------------------------------------------------------------- ----------------------------------------------------------------------- Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Volker Rieke Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt ----------------------------------------------------------------------- ----------------------------------------------------------------------- |
From: D B. <ba...@aw...> - 2020-03-19 16:59:31
|
Hi, is it possible to serve different entity attributes to different SPs with unity? Say I want to serve the username as "urn:mace:dir:attribute-def:cn" to one SP but as "username" to another. Is that feasible? Cheers, D |
From: Krzysztof B. <kb...@un...> - 2020-03-19 08:46:38
|
Hi, W dniu 18.03.2020 o 13:32, Shiraz Memon pisze: > Hi Krzysztof, > > I have found a non-crucial UI bug. So, as soon as I update any > registration form, unity moves to another position in the forms list. > > Image suffixed with ...13-16-34.png shows a list of registration forms > defined in my instance, please note the orcid form at the top. The > other image (...13-17-35.png) shows the orcid form which has moved to > the bottom as a result of small update. Is the behavior intended? Well, by default the list is not sorted. But you can click on any column header and sort it :-) > > By the way, some meta-information about the forms, e.g. creation and > last-modified date would be helpful. perhaps, but currently we don't have this metadata persisted for forms, so nothing to show. Best KB |
From: Krzysztof B. <kb...@un...> - 2020-03-19 08:34:43
|
W dniu 18.03.2020 o 11:35, D Baum pisze: > Ah, thanks, that solves my issue! > > Nonetheless, some suggestions for your backlog regarding UX: > Having attributes listed as [0] through [4] is not very straightforward > for editing, the attribute name would be more intuitive. > Or you could add the "reorder" button that exists in the profile action > page also to the page for editing the collected attributes. Yes, we are aware of this. Simply put that's quite a bit of work on a rather rarely used functionality, so rather far in the queue. |
From: Shiraz M. <a....@fz...> - 2020-03-18 12:33:19
|
Hi Krzysztof, I have found a non-crucial UI bug. So, as soon as I update any registration form, unity moves to another position in the forms list. Image suffixed with ...13-16-34.png shows a list of registration forms defined in my instance, please note the orcid form at the top. The other image (...13-17-35.png) shows the orcid form which has moved to the bottom as a result of small update. Is the behavior intended? By the way, some meta-information about the forms, e.g. creation and last-modified date would be helpful. Thanks, Shiraz -- Shiraz Memon Federated Systems and Data Jülich Supercomputing Centre (JSC) Phone: +49 2461 61 6899 Fax: +49 2461 61 6656 ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Volker Rieke Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ |
From: D B. <ba...@aw...> - 2020-03-18 11:07:14
|
Huh, it started working now, metadata now contains SLO info. Maybe I missed a restart? In any case, you can ignore the question :-) On 17/03/2020 20:48, D Baum wrote: > Hi, > > I'm trying to configure a remote SAML authenticator. > > In conf/modules/saml/samlAuthenticator.properties, I've set these options: > > unity.saml.requester.metadataPath=metadata > unity.saml.requester.sloPath=slo > unity.saml.requester.sloRealm=default > > When I access unity's SP metadata file at > https://myunity/unitygw/saml-sp-metadata/metadata > it contains the AssertionConsumerService but no SingleLogoutService > description. > > The SLO itself seems to be available OK at > https://myunity/unitygw/SPSLO/WEB/slo > > Can I make unity include the SLO URL in the autogenerated SP metadata? > > Cheers, > D > |
From: D B. <ba...@aw...> - 2020-03-18 10:35:56
|
Ah, thanks, that solves my issue! Nonetheless, some suggestions for your backlog regarding UX: Having attributes listed as [0] through [4] is not very straightforward for editing, the attribute name would be more intuitive. Or you could add the "reorder" button that exists in the profile action page also to the page for editing the collected attributes. Cheers, D On 18/03/2020 10:36, Krzysztof Benedyczak wrote: > Hi, > > W dniu 17.03.2020 o 15:44, D Baum pisze: >> Hi! >> >> On 14/03/2020 11:04, Krzysztof Benedyczak wrote: >>> For the current unity: >>> >>> first of all you need to set >>> >>> unityServer.core.allowFullHtml=true >>> >>> in unityServer.conf. This turns off some of the XSS prevention measures, >>> basically trusting admin-entered HTML. >>> >>> Then you can configure your registration form agreement with a link, >>> like this: >>> >>> I agree to <a href="https://example.com/tou.html" target="_blank">ToU</a> >> Perfect, thanks! >> >> BTW: Is there a way to re-order the form elements? > > Yes. Just enable custom layout > > > HTH, > KB > |