[GitHub] [syncope] dependabot[bot] closed pull request #459: Bump mssql-jdbc from 12.2.0.jre11 to 12.3.0.jre11-preview
dependabot[bot] closed pull request #459: Bump mssql-jdbc from 12.2.0.jre11 to 12.3.0.jre11-preview URL: https://github.com/apache/syncope/pull/459 -- 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
[GitHub] [syncope] ilgrosso commented on pull request #459: Bump mssql-jdbc from 12.2.0.jre11 to 12.3.0.jre11-preview
ilgrosso commented on PR #459: URL: https://github.com/apache/syncope/pull/459#issuecomment-1537040018 @dependabot close -- 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
[GitHub] [syncope] dependabot[bot] opened a new pull request, #459: Bump mssql-jdbc from 12.2.0.jre11 to 12.3.0.jre11-preview
dependabot[bot] opened a new pull request, #459: URL: https://github.com/apache/syncope/pull/459 Bumps [mssql-jdbc](https://github.com/Microsoft/mssql-jdbc) from 12.2.0.jre11 to 12.3.0.jre11-preview. Release notes Sourced from https://github.com/Microsoft/mssql-jdbc/releases;>mssql-jdbc's releases. [12.2.0] Stable Release Added Added new connection property datetimeParameterType to specify datatype to use for date/timestamp parameters https://redirect.github.com/microsoft/mssql-jdbc/pull/1590;>1590 Changed Renamed driver DefaultAzureCredential authentication to ActiveDirectoryDefault https://redirect.github.com/microsoft/mssql-jdbc/pull/2055;>2055 Update to dynamically check for ExtendedSocketOption class https://redirect.github.com/microsoft/mssql-jdbc/pull/2043;>2043 Upgraded dependency versions https://redirect.github.com/microsoft/mssql-jdbc/pull/2040;>2040 https://redirect.github.com/microsoft/mssql-jdbc/pull/1966;>1966 Misc code cleanup and test fixes https://redirect.github.com/microsoft/mssql-jdbc/pull/2059;>2059 https://redirect.github.com/microsoft/mssql-jdbc/pull/2053;>2053 https://redirect.github.com/microsoft/mssql-jdbc/pull/2049;>2049 https://redirect.github.com/microsoft/mssql-jdbc/pull/2048;>2048 https://redirect.github.com/microsoft/mssql-jdbc/pull/2044;>2044 https://redirect.github.com/microsoft/mssql-jdbc/pull/2041;>2041 https://redirect.github.com/microsoft/mssql-jdbc/pull/2031;>2031 https://github.com/microsoft/mssql-jdbc/pull2029;>2029 https://redirect.github.com/microsoft/mssql-jdbc/pull/2016;>2016 https://redirect.github.com/microsoft/mssql-jdbc/pull/2014;>2014 https://redirect.github.com/microsoft/mssql-jdbc/pull/1991;>1991 https://redirect.github.com/microsoft/mssql-jdbc/pull/1977;>1977 https://redirect.github .com/microsoft/mssql-jdbc/pull/1974">1974 https://redirect.github.com/microsoft/mssql-jdbc/pull/1970;>1970 https://redirect.github.com/microsoft/mssql-jdbc/pull/1969;>1969 https://redirect.github.com/microsoft/mssql-jdbc/pull/1962;>1962 Fixed issues Fixed BigDecimal Precision/Scale issue https://redirect.github.com/microsoft/mssql-jdbc/pull/2051;>2051 Fixed NULL state and 0 error code for SQL exceptions https://redirect.github.com/microsoft/mssql-jdbc/pull/2018;>2018 Fixed incorrect updateCount https://redirect.github.com/microsoft/mssql-jdbc/pull/2013;>2013 Fixed Azure Active Directory user name cache matching to be case insensitive https://redirect.github.com/microsoft/mssql-jdbc/pull/1923;>1923 Fixed concurrency issues in encrypt/decrypt obfuscation methods for truststore password https://redirect.github.com/microsoft/mssql-jdbc/pull/1968;>1968 Fixed Idle Connection recovery so that unprocessedResponseCount isn't over decremented https://redirect.github.com/microsoft/mssql-jdbc/pull/1989;>1989 Fixed race condition connecting to the wrong SQLServer host in configurable IPv6 https://redirect.github.com/microsoft/mssql-jdbc/pull/1968;>1968 Commits See full diff in https://github.com/Microsoft/mssql-jdbc/commits;>compare view [](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 options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it
[jira] [Created] (SYNCOPE-1757) Misalignment between SyncTokenSerializer and SyncTokenDeserializer in case of token given as a clear string
Fabio Martelli created SYNCOPE-1757:
---
Summary: Misalignment between SyncTokenSerializer and
SyncTokenDeserializer in case of token given as a clear string
Key: SYNCOPE-1757
URL: https://issues.apache.org/jira/browse/SYNCOPE-1757
Project: Syncope
Issue Type: Bug
Components: core
Affects Versions: 3.0.3
Reporter: Fabio Martelli
Fix For: 3.0.4
If resource connector provides a syncToken as a clear string and if this string
is Base64 deserializable (i.e.AD uSNChanged "1934664") than serialization
works fine ("syncToken":"\{\"value\":\"1934664\"}") but deserialization needed
to ask for a new incremental PULL. In fact in this case the value is
deserialized as a byte array because deserialized Base64.
This behaviour cause the failure of the incremental PULL.
[https://github.com/apache/syncope/blob/3_0_X/core/provisioning-api/src/main/java/org/apache/syncope/core/provisioning/api/serialization/SyncTokenDeserializer.java]
[https://github.com/apache/syncope/blob/3_0_X/core/provisioning-api/src/main/java/org/apache/syncope/core/provisioning/api/serialization/SyncTokenSerializer.java]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [VOTE] Apache Syncope 2.1.14
Here's my +1. Best regards, Samuel Il 05/05/23 16:29, Francesco Chicchiriccò ha scritto: I've created a 2.1.14 release, with the following artifacts up for a vote: Please note that GIT links are not from gitbox.apache.org as usual, but from GitHub mirror due to current incident https://status.apache.org/incidents/y1t4w1bx0bc9 GIT source tag (2bc40ed425): https://github.com/apache/syncope/releases/tag/syncope-2.1.14 List of changes: https://github.com/apache/syncope/blob/syncope-2.1.14/CHANGES Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.1.14/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1082/ Staging site (not a typo, it is the same as for 3.0.3 being under vote): https://syncope.apache.org/3.0.3/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards.
Re: [VOTE] Apache Syncope 3.0.3
Here's my +1. Best regards, Il giorno ven 5 mag 2023 alle ore 11:22 Francesco Chicchiriccò < ilgro...@apache.org> ha scritto: > I've created a 3.0.3 release, with the following artifacts up for a vote: > > Please note that GIT links are not from gitbox.apache.org as usual, but > from GitHub mirror due to current incident > https://status.apache.org/incidents/y1t4w1bx0bc9 > > GIT source tag (7350b35933): > https://github.com/apache/syncope/releases/tag/syncope-3.0.3 > > List of changes: > https://github.com/apache/syncope/blob/syncope-3.0.3/CHANGES > > Staging artifacts: > https://dist.apache.org/repos/dist/dev/syncope/3.0.3/ > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachesyncope-1081/ > > Staging site: > https://syncope.apache.org/3.0.3/index.html > > PGP release keys (signed using 273DF287): > http://www.apache.org/dist/syncope/KEYS > > Vote will be open for 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Here's my +1 > Regards. > > -- > Francesco Chicchiriccò > > Tirasa - Open Source Excellence > http://www.tirasa.net/ > > Member at The Apache Software Foundation > Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail > http://home.apache.org/~ilgrosso/ > > -- -- Lorenzo Di Cola Software Engineer @ Tirasa S.r.l. Viale Vittoria Colonna, 97 - 65127 Pescara Tel +39 0859116307 / FAX +39 085973http://www.tirasa.net Apache Syncope Committerhttp://people.apache.org/phonebook.html?uid=loredicola
Re: [VOTE] Apache Syncope 2.1.14
Here's my +1. Best regards, Il giorno ven 5 mag 2023 alle ore 16:29 Francesco Chicchiriccò < ilgro...@apache.org> ha scritto: > I've created a 2.1.14 release, with the following artifacts up for a vote: > > Please note that GIT links are not from gitbox.apache.org as usual, but > from GitHub mirror due to current incident > https://status.apache.org/incidents/y1t4w1bx0bc9 > > GIT source tag (2bc40ed425): > https://github.com/apache/syncope/releases/tag/syncope-2.1.14 > > List of changes: > https://github.com/apache/syncope/blob/syncope-2.1.14/CHANGES > > Staging artifacts: > https://dist.apache.org/repos/dist/dev/syncope/2.1.14/ > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachesyncope-1082/ > > Staging site (not a typo, it is the same as for 3.0.3 being under vote): > https://syncope.apache.org/3.0.3/index.html > > PGP release keys (signed using 273DF287): > http://www.apache.org/dist/syncope/KEYS > > Vote will be open for 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > Here's my +1 > Regards. > > -- > Francesco Chicchiriccò > > Tirasa - Open Source Excellence > http://www.tirasa.net/ > > Member at The Apache Software Foundation > Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail > http://home.apache.org/~ilgrosso/ > > -- -- Lorenzo Di Cola Software Engineer @ Tirasa S.r.l. Viale Vittoria Colonna, 97 - 65127 Pescara Tel +39 0859116307 / FAX +39 085973http://www.tirasa.net Apache Syncope Committerhttp://people.apache.org/phonebook.html?uid=loredicola
[VOTE] Apache Syncope 2.1.14
I've created a 2.1.14 release, with the following artifacts up for a vote: Please note that GIT links are not from gitbox.apache.org as usual, but from GitHub mirror due to current incident https://status.apache.org/incidents/y1t4w1bx0bc9 GIT source tag (2bc40ed425): https://github.com/apache/syncope/releases/tag/syncope-2.1.14 List of changes: https://github.com/apache/syncope/blob/syncope-2.1.14/CHANGES Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.1.14/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1082/ Staging site (not a typo, it is the same as for 3.0.3 being under vote): https://syncope.apache.org/3.0.3/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[jira] [Commented] (SYNCOPE-1755) NullPointer exception during PULL delete operation in case of NO_MATCH
[ https://issues.apache.org/jira/browse/SYNCOPE-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17719857#comment-17719857 ] ASF subversion and git services commented on SYNCOPE-1755: -- Commit 05b8d64a77de3c21e69eb213f39e121926bce3df in syncope's branch refs/heads/2_1_X from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=05b8d64a77 ] [SYNCOPE-1755] Reworking the provided fix > NullPointer exception during PULL delete operation in case of NO_MATCH > -- > > Key: SYNCOPE-1755 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1755 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 3.0.3 >Reporter: Fabio Martelli >Assignee: Fabio Martelli >Priority: Major > Fix For: 2.1.14, 3.0.4, 4.0.0 > > > During PULL, occurrence of a DELETE operation generates a NullPointer > exception in case of NO_MATCH. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [VOTE] Apache Syncope 3.0.3
+1. Best regards, Samuel Il 05/05/23 11:22, Francesco Chicchiriccò ha scritto: I've created a 3.0.3 release, with the following artifacts up for a vote: Please note that GIT links are not from gitbox.apache.org as usual, but from GitHub mirror due to current incident https://status.apache.org/incidents/y1t4w1bx0bc9 GIT source tag (7350b35933): https://github.com/apache/syncope/releases/tag/syncope-3.0.3 List of changes: https://github.com/apache/syncope/blob/syncope-3.0.3/CHANGES Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/3.0.3/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1081/ Staging site: https://syncope.apache.org/3.0.3/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards.
[jira] [Resolved] (SYNCOPE-1755) NullPointer exception during PULL delete operation in case of NO_MATCH
[ https://issues.apache.org/jira/browse/SYNCOPE-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-1755. - Resolution: Fixed > NullPointer exception during PULL delete operation in case of NO_MATCH > -- > > Key: SYNCOPE-1755 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1755 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 3.0.3 >Reporter: Fabio Martelli >Assignee: Fabio Martelli >Priority: Major > Fix For: 2.1.14, 3.0.4, 4.0.0 > > > During PULL, occurrence of a DELETE operation generates a NullPointer > exception in case of NO_MATCH. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1755) NullPointer exception during PULL delete operation in case of NO_MATCH
[ https://issues.apache.org/jira/browse/SYNCOPE-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17719795#comment-17719795 ] ASF subversion and git services commented on SYNCOPE-1755: -- Commit 1b94827b11c920a5bf5a99354b86fd81cca392d4 in syncope's branch refs/heads/2_1_X from Fabio Martelli [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=1b94827b11 ] [SYNCOPE-1755] Skip delete operation in case of NO_MATCH (#457) > NullPointer exception during PULL delete operation in case of NO_MATCH > -- > > Key: SYNCOPE-1755 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1755 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 3.0.3 >Reporter: Fabio Martelli >Assignee: Fabio Martelli >Priority: Major > Fix For: 2.1.14, 3.0.4, 4.0.0 > > > During PULL, occurrence of a DELETE operation generates a NullPointer > exception in case of NO_MATCH. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1755) NullPointer exception during PULL delete operation in case of NO_MATCH
[ https://issues.apache.org/jira/browse/SYNCOPE-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17719792#comment-17719792 ] ASF subversion and git services commented on SYNCOPE-1755: -- Commit c9f7a86ff4ec22d9a59e4712f6b1be10f1086aa1 in syncope's branch refs/heads/master from Fabio Martelli [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=c9f7a86ff4 ] [SYNCOPE-1755] Skip delete operation in case of NO_MATCH (#457) > NullPointer exception during PULL delete operation in case of NO_MATCH > -- > > Key: SYNCOPE-1755 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1755 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 3.0.3 >Reporter: Fabio Martelli >Assignee: Fabio Martelli >Priority: Major > Fix For: 2.1.14, 3.0.4, 4.0.0 > > > During PULL, occurrence of a DELETE operation generates a NullPointer > exception in case of NO_MATCH. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1755) NullPointer exception during PULL delete operation in case of NO_MATCH
[ https://issues.apache.org/jira/browse/SYNCOPE-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17719791#comment-17719791 ] ASF subversion and git services commented on SYNCOPE-1755: -- Commit f257752a0e5be2f1dd917263d24e4aa00d0ee2be in syncope's branch refs/heads/3_0_X from Fabio Martelli [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=f257752a0e ] [SYNCOPE-1755] Skip delete operation in case of NO_MATCH (#457) > NullPointer exception during PULL delete operation in case of NO_MATCH > -- > > Key: SYNCOPE-1755 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1755 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 3.0.3 >Reporter: Fabio Martelli >Assignee: Fabio Martelli >Priority: Major > Fix For: 2.1.14, 3.0.4, 4.0.0 > > > During PULL, occurrence of a DELETE operation generates a NullPointer > exception in case of NO_MATCH. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [syncope] fmartelli merged pull request #457: [SYNCOPE-1755] Skip delete operation in case of NO_MATCH
fmartelli merged PR #457: URL: https://github.com/apache/syncope/pull/457 -- 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
[jira] [Assigned] (SYNCOPE-1756) Add an id_token_hint parameter to the logout provider url for OIDC
[ https://issues.apache.org/jira/browse/SYNCOPE-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò reassigned SYNCOPE-1756: --- Assignee: Francesco Chicchiriccò > Add an id_token_hint parameter to the logout provider url for OIDC > -- > > Key: SYNCOPE-1756 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1756 > Project: Syncope > Issue Type: Bug > Components: extensions >Affects Versions: 2.1.13 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.1.14 > > > Some OIDC providers also require the id_token_hint parameter in the logout url -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SYNCOPE-1756) Add an id_token_hint parameter to the logout provider url for OIDC
[ https://issues.apache.org/jira/browse/SYNCOPE-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-1756. - Resolution: Fixed > Add an id_token_hint parameter to the logout provider url for OIDC > -- > > Key: SYNCOPE-1756 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1756 > Project: Syncope > Issue Type: Bug > Components: extensions >Affects Versions: 2.1.13 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.1.14 > > > Some OIDC providers also require the id_token_hint parameter in the logout url -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1756) Add an id_token_hint parameter to the logout provider url for OIDC
[ https://issues.apache.org/jira/browse/SYNCOPE-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17719790#comment-17719790 ] ASF subversion and git services commented on SYNCOPE-1756: -- Commit b5b53d58aef18d061e494273d2a3dbdc9ea86936 in syncope's branch refs/heads/2_1_X from Valerio Crescia [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=b5b53d58ae ] [SYNCOPE-1756] add id_token_hint to OIDC Logout request (#458) > Add an id_token_hint parameter to the logout provider url for OIDC > -- > > Key: SYNCOPE-1756 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1756 > Project: Syncope > Issue Type: Bug > Components: extensions >Affects Versions: 2.1.13 >Reporter: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.1.14 > > > Some OIDC providers also require the id_token_hint parameter in the logout url -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [syncope] ilgrosso merged pull request #458: [SYNCOPE-1756] add id_token_hint to OIDC Logout request
ilgrosso merged PR #458: URL: https://github.com/apache/syncope/pull/458 -- 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
[GitHub] [syncope] fmartelli opened a new pull request, #457: [SYNCOPE-1755] Skip delete operation in case of NO_MATCH
fmartelli opened a new pull request, #457: URL: https://github.com/apache/syncope/pull/457 Skip delete operation in case of NO_MATCH -- 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
[jira] [Created] (SYNCOPE-1756) Add an id_token_hint parameter to the logout provider url for OIDC
Marco Di Sabatino Di Diodoro created SYNCOPE-1756: - Summary: Add an id_token_hint parameter to the logout provider url for OIDC Key: SYNCOPE-1756 URL: https://issues.apache.org/jira/browse/SYNCOPE-1756 Project: Syncope Issue Type: Bug Components: extensions Affects Versions: 2.1.13 Reporter: Marco Di Sabatino Di Diodoro Fix For: 2.1.14 Some OIDC providers also require the id_token_hint parameter in the logout url -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SYNCOPE-1755) NullPointer exception during PULL delete operation in case of NO_MATCH
Fabio Martelli created SYNCOPE-1755: --- Summary: NullPointer exception during PULL delete operation in case of NO_MATCH Key: SYNCOPE-1755 URL: https://issues.apache.org/jira/browse/SYNCOPE-1755 Project: Syncope Issue Type: Bug Components: core Affects Versions: 3.0.3 Reporter: Fabio Martelli Assignee: Fabio Martelli Fix For: 2.1.14, 3.0.4, 4.0.0 During PULL, occurrence of a DELETE operation generates a NullPointer exception in case of NO_MATCH. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[VOTE] Apache Syncope 3.0.3
I've created a 3.0.3 release, with the following artifacts up for a vote: Please note that GIT links are not from gitbox.apache.org as usual, but from GitHub mirror due to current incident https://status.apache.org/incidents/y1t4w1bx0bc9 GIT source tag (7350b35933): https://github.com/apache/syncope/releases/tag/syncope-3.0.3 List of changes: https://github.com/apache/syncope/blob/syncope-3.0.3/CHANGES Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/3.0.3/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1081/ Staging site: https://syncope.apache.org/3.0.3/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[GitHub] [syncope] ilgrosso merged pull request #456: Bump xalan from 2.7.2 to 2.7.3
ilgrosso merged PR #456: URL: https://github.com/apache/syncope/pull/456 -- 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
[jira] [Updated] (SYNCOPE-1662) Leverage MariaDB JSON type
[ https://issues.apache.org/jira/browse/SYNCOPE-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1662: Fix Version/s: 3.0.4 (was: 3.0.3) > Leverage MariaDB JSON type > -- > > Key: SYNCOPE-1662 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1662 > Project: Syncope > Issue Type: New Feature > Components: core >Reporter: Francesco Chicchiriccò >Priority: Major > Labels: jpa, mariadb, persistence > Fix For: 3.0.4, 4.0.0 > > > Similar to SYNCOPE-1395 for PostgreSQL and SYNCOPE-1401 for MySQL, enhance > the JPA layer by empowering [MariaDB JSON > datatype|https://mariadb.com/kb/en/json-data-type/] for user, group and any > object attributes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SYNCOPE-1621) Allow export for individual items in XML
[ https://issues.apache.org/jira/browse/SYNCOPE-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1621: Fix Version/s: 3.0.4 (was: 3.0.3) > Allow export for individual items in XML > - > > Key: SYNCOPE-1621 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1621 > Project: Syncope > Issue Type: Improvement > Components: console, core >Reporter: Andrea Patricelli >Priority: Major > Fix For: 3.0.4, 4.0.0 > > > Provide a functionality in the admin console (and from REST) that allows one > to view the XML configuration of an individual item. For example, an user > would be interested in seeing the XML representation of the new configuration > parameter, or it might be a user object, group, provisioning rules, etc. -- This message was sent by Atlassian Jira (v8.20.10#820010)
