Task #2253
open
Update AD connector artifact dependency
0%
Description
During public release of our AD connector, we had to change its artifact due to potential conflict with Tirasa ConnId artifacts.
New artifact is:
<dependency>
<groupId>eu.bcvsolutions.idm.connector.ad</groupId>
<artifactId>ad-connector</artifactId>
<version>1.3.4.29</version>
</dependency>
Can you please check/update the dependency in product? Thx.
AFAIK the connector should be already uploaded to Nexus under new artifact name.
Related issues
Updated by Petr Fišer almost 4 years ago
Also a note for the future development. We are moving all subsequent versions of this connector from maven-public-releases to maven-releases. I think this should not be a problem but better to say it aloud. :)
Updated by Radek Tomiška almost 4 years ago
If all product required artefacts will not be in some public repository, then product cannot be build by other contributor. This is the reason, why all product dependenies should be available without login to our nexus.
https://github.com/bcvsolutions/CzechIdMng/blob/develop/Realization/backend/parent/pom.xml
Updated by Petr Fišer almost 4 years ago
Radek Tomiška wrote:
If all product required artefacts will not be in some public repository, then product cannot be build by other contributor. This is the reason, why all product dependenies should be available without login to our nexus.
https://github.com/bcvsolutions/CzechIdMng/blob/develop/Realization/backend/parent/pom.xml
I see. So we need to keep this one's binaries public. Will do.
Updated by Petr Fišer over 3 years ago
Totally forgot about the ticket, sorry.
New connector is located in maven-public-releases, so we can bundle it into the product by default.
Current new artifact is
<dependency> <groupId>eu.bcvsolutions.idm.connector.ad</groupId> <artifactId>ad-connector</artifactId> <version>1.3.5</version> </dependency>
Updated by Vít Švanda over 3 years ago
- Assignee deleted (
Vít Švanda) - Target version set to 10.8.0
I tested new dependency locally and works well.
To add to the product, we need to create a change script (or init processor) to upgrade AD systems from version 1.3.4.27.
It may be a useful tool (bulk action) to change the system connector to another connector (for example, AD to WinRM or upgrade version).
After consulting with Roman, version 1.3.5 is tested and should be compatible with 1.3.4.27 (no change in EAV).
Updated by Roman Kučera about 3 years ago
- Related to Task #2681: Change package for this connector added
Updated by Roman Kučera about 3 years ago
- Related to Task #2682: Change package for this connector added