Re: [PR] Bump com.mysql:mysql-connector-j from 8.3.0 to 8.4.0 [syncope]

2024-04-30 Thread via GitHub


ilgrosso merged PR #706:
URL: https://github.com/apache/syncope/pull/706


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@syncope.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[PR] Bump com.mysql:mysql-connector-j from 8.3.0 to 8.4.0 [syncope]

2024-04-30 Thread via GitHub


dependabot[bot] opened a new pull request, #706:
URL: https://github.com/apache/syncope/pull/706

   Bumps 
[com.mysql:mysql-connector-j](https://github.com/mysql/mysql-connector-j) from 
8.3.0 to 8.4.0.
   
   Changelog
   Sourced from https://github.com/mysql/mysql-connector-j/blob/release/8.x/CHANGES;>com.mysql:mysql-connector-j's
 changelog.
   
   Changelog
   https://dev.mysql.com/doc/relnotes/connector-j/en/;>https://dev.mysql.com/doc/relnotes/connector-j/en/
   Version 8.4.0
   
   
   WL#15706, Add OpenTelemetry tracing.
   
   
   WL#16174, Support for VECTOR data type.
   
   
   Fix for Bug#36380711, Tests failing due to removal of deprecated 
features.
   
   
   Fix for Bug#113600 (Bug#36171575), Contribution: Fix join condition for 
retrieval of imported primary keys.
   Thanks to Henning Pöttker for his contribution.
   
   
   WL#16196, GPL License Exception Update.
   
   
   Fix for Bug#111031 (Bug#3539), Contribution: Update 
SyntaxRegressionTest.java.
   Thanks to Abby Palmero for her contribution.
   
   
   Fix for Bug#113599 (Bug#36171571), Contribution: Replace StringBuffer 
with StringBuilder in ValueEncoders.
   Thanks to Henning Pöttker for his contribution.
   
   
   Fix for Bug#91550 (Bug#28297874), DatabaseMetaData specifies incorrect 
extra name characters.
   
   
   Fix for Bug#113129 (Bug#36043145), setting the FetchSize on a Statement 
object does not affect.
   
   
   Fix for Bug#22931632, GETPARAMETERBINDINGS() ON A PS RETURNS NPE WHEN NOT 
ALL PARAMETERS ARE BOUND.
   
   
   WL#16147, Remove support for FIDO authentication.
   
   
   Fix for Bug#110286 (Bug#35152855), Only call Messages.getString(...) when 
it's needed (when the SQLException is thrown).
   Thanks to Janick Reynders for his contribution.
   
   
   Fix for Bug#23143279, CLIENT HANG WHEN LOADBALANCESTRATEGY IS 
BESTRESPONSETIME.
   
   
   Version 8.3.0
   
   
   Fix for Bug#107107 (Bug#34101635), Redundant Reset stmt when 
setting useServerPrepStmtscachePrepStmts to true.
   Thanks to Marcos Albe for his contribution.
   
   
   Fix for Bug#19845752, COMMENT PARSING IS NOT PROPER IN CONNECTOR JDBC.
   
   
   Fix for Bug#112884 (Bug#36043166), Setting a large timeout leads to 
errors when executing SQL.
   
   
   WL#16077, Upgrade 3rd party libraries and tools.
   
   
   WL#16074, Upgrade Protocol Buffers dependency to protobuf-java-3.25.1.
   
   
   Fix for Bug#35929119, Issue with mysql-connector-j 8.0.33 connector 
(XDEVAPI) - getsession is slow.
   
   
   
   
   ... (truncated)
   
   
   Commits
   
   https://github.com/mysql/mysql-connector-j/commit/1c3f5c149e0bfe31c7fbeb24e2d260cd890972c4;>1c3f5c1
 Documentation review for WL#15706 and WL#16174.
   https://github.com/mysql/mysql-connector-j/commit/5f2383dbbb8f020ebb4884673d5bc0f7b2488d88;>5f2383d
 Update fix for Bug#36380711, Tests failing due to removal of deprecated 
featu...
   https://github.com/mysql/mysql-connector-j/commit/b1da9624ba78afb39e1d338f4dd4942db4856315;>b1da962
 WL#15706, Add OpenTelemetry tracing.
   https://github.com/mysql/mysql-connector-j/commit/6758555135610fa88993d9e557d013e6e5248aa9;>6758555
 WL#16174, Support for VECTOR data type.
   https://github.com/mysql/mysql-connector-j/commit/6fbbd21ffcc9047b5923e9b9dc3edf31338e578e;>6fbbd21
 Fix for Bug#36380711, Tests failing due to removal of deprecated features.
   https://github.com/mysql/mysql-connector-j/commit/8b40d85d38f83781e940e2788474db0b89da10c2;>8b40d85
 Fix for Bug#113600 (Bug#36171575), Contribution: Fix join condition for 
retri...
   https://github.com/mysql/mysql-connector-j/commit/e629456623b5f5580ccd96485d36680f593f;>e629456
 WL#16196, GPL License Exception Update.
   https://github.com/mysql/mysql-connector-j/commit/c91a638b84898d808b08e3e17b0717e6e10c1a27;>c91a638
 Fix for Bug#111031 (Bug#3539), Contribution: Update 
SyntaxRegressionTest
   https://github.com/mysql/mysql-connector-j/commit/00449a4730d3d8eb945f05fb0bc40af309037931;>00449a4
 Fix for Bug#113599 (Bug#36171571), Contribution: Replace StringBuffer with 
St...
   https://github.com/mysql/mysql-connector-j/commit/832994a2072b733933824b668179590a7f59528d;>832994a
 Fix for Bug#91550 (Bug#28297874), DatabaseMetaData specifies incorrect extra 
...
   Additional commits viewable in https://github.com/mysql/mysql-connector-j/compare/8.3.0...8.4.0;>compare 
view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=com.mysql:mysql-connector-j=maven=8.3.0=8.4.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   
   Dependabot commands and 

[jira] [Updated] (SYNCOPE-1818) Wrong status value propagated to external resources if changed while pulling

2024-04-30 Thread Jira


 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-1818:

Description: 
In some specific cases the status of an user on an external resource could 
change remotely. If, simultaneously, some other attribute is changed and a 
propagation is fired the wrong status is propagated on the external resources.

For example, if an active (on syncope) user on resource-pull changes its 
surname, email and status (set to disabled) and a pull is fired, a propagation 
on some target resources occurs, depending on email and/or surname mapping. 
Propagation status is wrong, for example if pulled "disabled" the user is 
propagated active, i.e. {{__ENABLE__}} attribute is set to {{false}}. 

  was:
In some specific cases the status of an user on an external resource could 
change remotely. If, simultaneously, some other attribute is changed and a 
propagation is fired the wrong status is propagated on the external resources.

For example, if an active (on syncope) user on resource-pull changes its 
surname, email and status (set to disabled) and a pull is fired, a propagation 
on some target resources occurs, depending on email and/or surname mapping. 
Propagation status is wrong, for example if pulled "disabled" the user is 
propagated active, i.e. `__ENABLE__` attribute is set to `false`. 


> Wrong status value propagated to external resources if changed while pulling
> 
>
> Key: SYNCOPE-1818
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1818
> Project: Syncope
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.0.6
>Reporter: Andrea Patricelli
>Assignee: Andrea Patricelli
>Priority: Major
> Fix For: 3.0.7, 4.0.0
>
>
> In some specific cases the status of an user on an external resource could 
> change remotely. If, simultaneously, some other attribute is changed and a 
> propagation is fired the wrong status is propagated on the external resources.
> For example, if an active (on syncope) user on resource-pull changes its 
> surname, email and status (set to disabled) and a pull is fired, a 
> propagation on some target resources occurs, depending on email and/or 
> surname mapping. Propagation status is wrong, for example if pulled 
> "disabled" the user is propagated active, i.e. {{__ENABLE__}} attribute is 
> set to {{false}}. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Assigned] (SYNCOPE-1818) Wrong status value propagated to external resources if changed while pulling

2024-04-30 Thread Andrea Patricelli (Jira)


 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Patricelli reassigned SYNCOPE-1818:
--

Assignee: Andrea Patricelli

> Wrong status value propagated to external resources if changed while pulling
> 
>
> Key: SYNCOPE-1818
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1818
> Project: Syncope
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.0.6
>Reporter: Andrea Patricelli
>Assignee: Andrea Patricelli
>Priority: Major
> Fix For: 3.0.7, 4.0.0
>
>
> In some specific cases the status of an user on an external resource could 
> change remotely. If, simultaneously, some other attribute is changed and a 
> propagation is fired the wrong status is propagated on the external resources.
> For example, if an active (on syncope) user on resource-pull changes its 
> surname, email and status (set to disabled) and a pull is fired, a 
> propagation on some target resources occurs, depending on email and/or 
> surname mapping. Propagation status is wrong, for example if pulled 
> "disabled" the user is propagated active, i.e. `__ENABLE__` attribute is set 
> to `false`. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


Re: [PR] [SYNCOPE-1818] fixes wrong status propagation while pulling a status … [syncope]

2024-04-30 Thread via GitHub


ilgrosso commented on code in PR #703:
URL: https://github.com/apache/syncope/pull/703#discussion_r1584174819


##
fit/core-reference/src/test/java/org/apache/syncope/fit/core/UserIssuesITCase.java:
##
@@ -1708,4 +1717,84 @@ public void issueSYNCOPE1809() throws IOException {
 SCHEMA_SERVICE.delete(SchemaType.PLAIN, 
externalKeySchemaTO.getKey());
 }
 }
+
+@Test
+void issueStatusNotPropagated() {

Review Comment:
   Please rename this method as `issueSYNCOPE1818`



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@syncope.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] Bump org.apache.maven.plugins:maven-deploy-plugin from 3.1.1 to 3.1.2 [syncope]

2024-04-30 Thread via GitHub


dependabot[bot] closed pull request #704: Bump 
org.apache.maven.plugins:maven-deploy-plugin from 3.1.1 to 3.1.2
URL: https://github.com/apache/syncope/pull/704


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@syncope.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] Bump org.codehaus.cargo:cargo-maven3-plugin from 1.10.12 to 1.10.13 [syncope]

2024-04-30 Thread via GitHub


ilgrosso commented on PR #705:
URL: https://github.com/apache/syncope/pull/705#issuecomment-2084439719

   @dependabot rebase


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@syncope.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] Bump org.apache.maven.plugins:maven-deploy-plugin from 3.1.1 to 3.1.2 [syncope]

2024-04-30 Thread via GitHub


dependabot[bot] commented on PR #704:
URL: https://github.com/apache/syncope/pull/704#issuecomment-2084441528

   Looks like org.apache.maven.plugins:maven-deploy-plugin is up-to-date now, 
so this is no longer needed.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@syncope.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] Bump org.codehaus.cargo:cargo-maven3-plugin from 1.10.12 to 1.10.13 [syncope]

2024-04-30 Thread via GitHub


dependabot[bot] commented on PR #705:
URL: https://github.com/apache/syncope/pull/705#issuecomment-2084440832

   Looks like org.codehaus.cargo:cargo-maven3-plugin is up-to-date now, so this 
is no longer needed.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@syncope.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] Bump org.codehaus.cargo:cargo-maven3-plugin from 1.10.12 to 1.10.13 [syncope]

2024-04-30 Thread via GitHub


dependabot[bot] closed pull request #705: Bump 
org.codehaus.cargo:cargo-maven3-plugin from 1.10.12 to 1.10.13
URL: https://github.com/apache/syncope/pull/705


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@syncope.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] Bump org.apache.maven.plugins:maven-deploy-plugin from 3.1.1 to 3.1.2 [syncope]

2024-04-30 Thread via GitHub


ilgrosso commented on PR #704:
URL: https://github.com/apache/syncope/pull/704#issuecomment-2084440622

   @dependabot rebase


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@syncope.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org