Menu
▾
▴
unity-idm-discuss
|
From: Sander A. <sa....@fz...> - 2025-12-09 15:38:53
Attachments:
smime.p7s
|
Dear Kryzsztof, dear Roman, TL;DR: max number of values is always 1 or unlimited. we found some strange behaviour when limiting the maximum numbers of value other to one. We created an attribute with type string and set min number of values to 1, max number of values to 5. We created 4 attribute statements which fill this attribute with values. Viewing this attribute of an user, which should contain two values, it contains only one value. Disabling the attribute statement of the shown values, makes appearing the second expected value. After enabling the first attribute statement, makes the first value appearing, the second is gone. After setting the number of values to unlimited in the Attribute types, both expected values appears. It seems unity ignores the number of max values but checks only if it is set to unlimited. We found this issue on unity 4.1.1. Best regards, Sander -- Large-Scale Data Science Juelich Supercomputing Centre phone: +49 2461 61 8847 fax: +49 2461 61 6656 email: sa....@fz... ----------------------------------------------------------------------- ----------------------------------------------------------------------- Forschungszentrum Jülich GmbH 52425 Jülich Sitz der Gesellschaft: Jülich Eingetragen im Handelsregister des Amtsgerichts Düren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Stefan Müller Geschäftsführung: Prof. Dr. Astrid Lambrecht (Vorsitzende), Dr. Stephanie Bauer (stellvertretende Vorsitzende), Prof. Dr. Ir. Pieter Jansens, Prof. Dr. Laurens Kuipers ----------------------------------------------------------------------- ----------------------------------------------------------------------- |
|
From: Roman K. <ro...@un...> - 2025-12-15 10:08:28
|
Dear Sander, This does look like something we should be able to reproduce, but we’ll need a bit more information to properly understand what’s happening and identify the root cause. Could you please help us with the following details: 1. Where exactly was the attribute value viewed? When you say “Viewing this attribute of a user”, could you clarify what UI/view (or API) you used? 2. Attribute type configuration: Could you share more details about the attribute type itself? A screenshot of the Attribute Type configuration would be ideal. 3. Attribute statements setup: A screenshot of the “Edit attribute statement” dialog for the relevant statements would be very helpful. With this information, we should be able to reproduce the issue and determine whether this is a configuration problem or a bug in Unity 4.1.1. Thanks in advance for your help. Best regards, Roman pon., 15 gru 2025 o 08:58 Roman Krysiński <ro...@au...> napisał(a): > Dear Sander, > > This does look like something we should be able to reproduce, but we’ll > need a bit more information to properly understand what’s happening and > identify the root cause. > > Could you please help us with the following details: > > 1. Where exactly was the attribute value viewed? > When you say “Viewing this attribute of a user”, could you clarify what > UI/view (or API) you used? > > 2. Attribute type configuration: Could you share more details about the > attribute type itself? > A screenshot of the Attribute Type configuration would be ideal. > > 3. Attribute statements setup: A screenshot of the “Edit attribute > statement” dialog for the relevant statements would be very helpful. > > With this information, we should be able to reproduce the issue and > determine whether this is a configuration problem or a bug in Unity 4.1.1. > > Thanks in advance for your help. > > Best regards, > Roman > > wt., 9 gru 2025 o 16:39 Sander Apweiler <sa....@fz...> > napisał(a): > >> Dear Kryzsztof, >> dear Roman, >> >> TL;DR: max number of values is always 1 or unlimited. >> >> we found some strange behaviour when limiting the maximum numbers of >> value other to one. We created an attribute with type string and set >> min number of values to 1, max number of values to 5. We created 4 >> attribute statements which fill this attribute with values. Viewing >> this attribute of an user, which should contain two values, it contains >> only one value. Disabling the attribute statement of the shown values, >> makes appearing the second expected value. After enabling the first >> attribute statement, makes the first value appearing, the second is >> gone. After setting the number of values to unlimited in the Attribute >> types, both expected values appears. It seems unity ignores the number >> of max values but checks only if it is set to unlimited. We found this >> issue on unity 4.1.1. >> >> Best regards, >> Sander >> >> -- >> Large-Scale Data Science >> Juelich Supercomputing Centre >> >> phone: +49 2461 61 8847 >> fax: +49 2461 61 6656 >> email: sa....@fz... >> >> ----------------------------------------------------------------------- >> ----------------------------------------------------------------------- >> Forschungszentrum Jülich GmbH >> 52425 Jülich >> Sitz der Gesellschaft: Jülich >> Eingetragen im Handelsregister des Amtsgerichts Düren Nr. HR B 3498 >> Vorsitzender des Aufsichtsrats: MinDir Stefan Müller >> Geschäftsführung: Prof. Dr. Astrid Lambrecht (Vorsitzende), >> Dr. Stephanie Bauer (stellvertretende Vorsitzende), >> Prof. Dr. Ir. Pieter Jansens, Prof. Dr. Laurens Kuipers >> ----------------------------------------------------------------------- >> ----------------------------------------------------------------------- >> >> >> >> _______________________________________________ >> Unity-idm-discuss mailing list >> Uni...@li... >> https://lists.sourceforge.net/lists/listinfo/unity-idm-discuss >> > |
|
From: Sander A. <sa....@fz...> - 2025-12-17 08:48:19
|
Dear Roman, I added the answers inline. On Mon, 2025-12-15 at 11:08 +0100, Roman Krysiński wrote: > Dear Sander, > > This does look like something we should be able to reproduce, but > we’ll need a bit more information to properly understand what’s > happening and identify the root cause. > > Could you please help us with the following details: > > 1. Where exactly was the attribute value viewed? > When you say “Viewing this attribute of a user”, could you clarify > what UI/view (or API) you used? The attribute was viewed in the directory browser of the console endpoint. > > 2. Attribute type configuration: Could you share more details about > the attribute type itself? > A screenshot of the Attribute Type configuration would be ideal. Is attached. > > 3. Attribute statements setup: A screenshot of the “Edit attribute > statement” dialog for the relevant statements would be very helpful. Added as well. I just add one of four attribute statements. The other one are just working and adding another attribute. I also just recognize there is another bug in the attribute statements. When I edit it, the tick box for use attribute from extra group is selected, although it was not selected before. Best regards, Sander > > With this information, we should be able to reproduce the issue and > determine whether this is a configuration problem or a bug in Unity > 4.1.1. > > Thanks in advance for your help. > > Best regards, > Roman > > pon., 15 gru 2025 o 08:58 Roman Krysiński <ro...@au...> > napisał(a): > > Dear Sander, > > > > This does look like something we should be able to reproduce, but > > we’ll need a bit more information to properly understand what’s > > happening and identify the root cause. > > > > Could you please help us with the following details: > > > > 1. Where exactly was the attribute value viewed? > > When you say “Viewing this attribute of a user”, could you clarify > > what UI/view (or API) you used? > > > > 2. Attribute type configuration: Could you share more details about > > the attribute type itself? > > A screenshot of the Attribute Type configuration would be ideal. > > > > 3. Attribute statements setup: A screenshot of the “Edit attribute > > statement” dialog for the relevant statements would be very > > helpful. > > > > With this information, we should be able to reproduce the issue and > > determine whether this is a configuration problem or a bug in Unity > > 4.1.1. > > > > Thanks in advance for your help. > > > > Best regards, > > Roman > > > > wt., 9 gru 2025 o 16:39 Sander Apweiler <sa....@fz...> > > napisał(a): > > > Dear Kryzsztof, > > > dear Roman, > > > > > > TL;DR: max number of values is always 1 or unlimited. > > > > > > we found some strange behaviour when limiting the maximum numbers > > > of > > > value other to one. We created an attribute with type string and > > > set > > > min number of values to 1, max number of values to 5. We created > > > 4 > > > attribute statements which fill this attribute with values. > > > Viewing > > > this attribute of an user, which should contain two values, it > > > contains > > > only one value. Disabling the attribute statement of the shown > > > values, > > > makes appearing the second expected value. After enabling the > > > first > > > attribute statement, makes the first value appearing, the second > > > is > > > gone. After setting the number of values to unlimited in the > > > Attribute > > > types, both expected values appears. It seems unity ignores the > > > number > > > of max values but checks only if it is set to unlimited. We found > > > this > > > issue on unity 4.1.1. > > > > > > Best regards, > > > Sander > > > -- Large-Scale Data Science Juelich Supercomputing Centre phone: +49 2461 61 8847 fax: +49 2461 61 6656 email: sa....@fz... ----------------------------------------------------------------------- ----------------------------------------------------------------------- Forschungszentrum Jülich GmbH 52425 Jülich Sitz der Gesellschaft: Jülich Eingetragen im Handelsregister des Amtsgerichts Düren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Stefan Müller Geschäftsführung: Prof. Dr. Astrid Lambrecht (Vorsitzende), Dr. Stephanie Bauer (stellvertretende Vorsitzende), Prof. Dr. Ir. Pieter Jansens, Prof. Dr. Laurens Kuipers ----------------------------------------------------------------------- ----------------------------------------------------------------------- |
Thanks for helping keep SourceForge clean.
X