[jira] [Commented] (SYNCOPE-1805) Upgrade Spring Framework and Security versions

2024-02-19 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/SYNCOPE-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17818483#comment-17818483
 ] 

ASF subversion and git services commented on SYNCOPE-1805:
--

Commit 99c5aa5c3306d9c99675c167fd26955e98cca777 in syncope's branch 
refs/heads/3_0_X from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=99c5aa5c33 ]

[SYNCOPE-1805] Upgrading Spring Framework and Security to latest versions 
compatible with Spring Boot 2.7 (#623)



> Upgrade Spring Framework and Security versions
> --
>
> Key: SYNCOPE-1805
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1805
> Project: Syncope
>  Issue Type: Task
>Affects Versions: 3.0.6
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 3.0.7
>
>
> The current versions for Spring Framework and Security are pulled from Spring 
> Boot 2.7.18 BOM and are respectively:
> * 5.3.31
> * 5.7.11
> Considering that [Spring Boot 2.7 will not have further maintenance 
> releases|https://spring.io/blog/2023/11/23/spring-boot-2-7-18-available-now#end-of-open-source-support-for-spring-boot-2x],
>  we need to upgrade the two versions above to:
> * 5.3.32
> * 5.8.10
> Switching to Spring Security 5.8, in particular, will allow more space for 
> open source support: see https://spring.io/projects/spring-security#support



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


[jira] [Resolved] (SYNCOPE-1805) Upgrade Spring Framework and Security versions

2024-02-19 Thread Jira


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

Francesco Chicchiriccò resolved SYNCOPE-1805.
-
Resolution: Fixed

> Upgrade Spring Framework and Security versions
> --
>
> Key: SYNCOPE-1805
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1805
> Project: Syncope
>  Issue Type: Task
>Affects Versions: 3.0.6
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 3.0.7
>
>
> The current versions for Spring Framework and Security are pulled from Spring 
> Boot 2.7.18 BOM and are respectively:
> * 5.3.31
> * 5.7.11
> Considering that [Spring Boot 2.7 will not have further maintenance 
> releases|https://spring.io/blog/2023/11/23/spring-boot-2-7-18-available-now#end-of-open-source-support-for-spring-boot-2x],
>  we need to upgrade the two versions above to:
> * 5.3.32
> * 5.8.10
> Switching to Spring Security 5.8, in particular, will allow more space for 
> open source support: see https://spring.io/projects/spring-security#support



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


Re: [PR] [SYNCOPE-1805] Upgrading Spring Framework and Security to latest versions compatible with Spring Boot 2.7 [syncope]

2024-02-19 Thread via GitHub


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


-- 
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-1805) Upgrade Spring Framework and Security versions

2024-02-19 Thread Jira


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

Francesco Chicchiriccò updated SYNCOPE-1805:

Affects Version/s: 3.0.6

> Upgrade Spring Framework and Security versions
> --
>
> Key: SYNCOPE-1805
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1805
> Project: Syncope
>  Issue Type: Task
>Affects Versions: 3.0.6
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
>Priority: Major
> Fix For: 3.0.7
>
>
> The current versions for Spring Framework and Security are pulled from Spring 
> Boot 2.7.18 BOM and are respectively:
> * 5.3.31
> * 5.7.11
> Considering that [Spring Boot 2.7 will not have further maintenance 
> releases|https://spring.io/blog/2023/11/23/spring-boot-2-7-18-available-now#end-of-open-source-support-for-spring-boot-2x],
>  we need to upgrade the two versions above to:
> * 5.3.32
> * 5.8.10
> Switching to Spring Security 5.8, in particular, will allow more space for 
> open source support: see https://spring.io/projects/spring-security#support



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


[jira] [Created] (SYNCOPE-1805) Upgrade Spring Framework and Security versions

2024-02-19 Thread Jira
Francesco Chicchiriccò created SYNCOPE-1805:
---

 Summary: Upgrade Spring Framework and Security versions
 Key: SYNCOPE-1805
 URL: https://issues.apache.org/jira/browse/SYNCOPE-1805
 Project: Syncope
  Issue Type: Task
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
 Fix For: 3.0.7


The current versions for Spring Framework and Security are pulled from Spring 
Boot 2.7.18 BOM and are respectively:

* 5.3.31
* 5.7.11

Considering that [Spring Boot 2.7 will not have further maintenance 
releases|https://spring.io/blog/2023/11/23/spring-boot-2-7-18-available-now#end-of-open-source-support-for-spring-boot-2x],
 we need to upgrade the two versions above to:

* 5.3.32
* 5.8.10

Switching to Spring Security 5.8, in particular, will allow more space for open 
source support: see https://spring.io/projects/spring-security#support



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


Re: String value length

2024-02-19 Thread GCHQDeveloper29
Hi Francesco,

Awesome, thank you very much for clarifying that for me.

Regards,
GCHQDeveloper29

On Saturday, 17 February 2024 at 07:21, Francesco Chicchiriccò 
 wrote:

> On 16/02/24 19:36, GCHQDeveloper29 wrote:
> 
> > Hi Francesco,
> > 
> > Thank you for your timely response.
> > I have tried to insert the following snippet into my spring-orm.xml file 
> > (before the  and after the  for 
> > "org.apache.syncope.core.persistence.jpa.entity.group.JPAGPlainAttrUniqueValue",
> >  however it still appears to be creating as a VARCHAR(255) on postgresql as 
> > if the overrides are being ignored - if I have been a fool please do let me 
> > know.
> > 
> >  > class="org.apache.syncope.core.persistence.jpa.entity.anyobject.JPAAPlainAttrValue">
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >  > class="org.apache.syncope.core.persistence.jpa.entity.user.JPAUPlainAttrValue">
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >  > class="org.apache.syncope.core.persistence.jpa.entity.group.JPAGPlainAttrValue">
> > 
> > 
> > 
> > 
> > 
> > 
> 
> 
> Hi,
> as you have correctly reported before, the column whose mapping you want to 
> change is declared as field in AbstractPlainAttrValue, so you need to add 
> something like:
> 
>  class="org.apache.syncope.core.persistence.jpa.entity.AbstractPlainAttrValue">
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> right before the first  element in the file (see the declared XSD 
> for more information).
> 
> 
> As already said, please double check which ORM file you are effectively 
> using: there are different ones in fact for:
> 
> * PostgreSQL with JSONB support
> * MySQL with JSON support
> * Oracle, default or with JSON support
> * SQL server
> 
> if you are not in any of these 4 cases, then the default spring-orm.xml will 
> apply.
> 
> HTH
> Regards.
> 
> > On Friday, 16 February 2024 at 14:49, Francesco Chicchiriccò 
> > ilgro...@apache.org wrote:
> > 
> > > On 16/02/24 15:40, GCHQDeveloper29 wrote:
> > > 
> > > > Currently, string value'd schema are limited to 255 characters in 
> > > > length due to OpenJPA defaults.
> > > > It would be beneficial to either have this length as adjustable, 
> > > > increased or converted to a Lob.
> > > > The relevant code is within 
> > > > core/persistence-jpa/src/main/java/org/apache/syncope/core/persistence/jpa/entity/AbstractPlainAttrValue.java
> > > 
> > > Hi,
> > > you should be able to tweak any column definition by adjusting your local 
> > > ORM file.
> > > The actual file to change is the one indicated by the
> > > 
> > > persistence.domain[0].orm
> > > 
> > > property, e.g. spring-orm.xml by default.
> > > 
> > > The OpenJPA settings will in fact get metadata definitions both from Java 
> > > annotations (which are in fact immutable) and ORM xml file, with the 
> > > latter taking precedence over the former.
> > > 
> > > HTH
> > > 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] [Resolved] (SYNCOPE-1803) Can't remove multivalue membership plain schema value from console

2024-02-19 Thread Samuel Garofalo (Jira)


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

Samuel Garofalo resolved SYNCOPE-1803.
--
Resolution: Fixed

> Can't remove multivalue membership plain schema value from console
> --
>
> Key: SYNCOPE-1803
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1803
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 3.0.6
>Reporter: Samuel Garofalo
>Assignee: Samuel Garofalo
>Priority: Major
> Fix For: 3.0.7, 4.0.0
>
>
> If a multivalue membership plain schema has only one value and it's deleted 
> from the console, the value is not deleted.



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


[jira] [Assigned] (SYNCOPE-1803) Can't remove multivalue membership plain schema value from console

2024-02-19 Thread Samuel Garofalo (Jira)


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

Samuel Garofalo reassigned SYNCOPE-1803:


Assignee: Samuel Garofalo

> Can't remove multivalue membership plain schema value from console
> --
>
> Key: SYNCOPE-1803
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1803
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 3.0.6
>Reporter: Samuel Garofalo
>Assignee: Samuel Garofalo
>Priority: Major
> Fix For: 3.0.7, 4.0.0
>
>
> If a multivalue membership plain schema has only one value and it's deleted 
> from the console, the value is not deleted.



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


[jira] [Commented] (SYNCOPE-1803) Can't remove multivalue membership plain schema value from console

2024-02-19 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/SYNCOPE-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17818445#comment-17818445
 ] 

ASF subversion and git services commented on SYNCOPE-1803:
--

Commit df729ffd2c46001de81e8d0de9113b427bdf7e3a in syncope's branch 
refs/heads/master from Samuel Garofalo
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=df729ffd2c ]

[SYNCOPE-1803] Allow removing of all membership plain schemas value from 
console (#622)



> Can't remove multivalue membership plain schema value from console
> --
>
> Key: SYNCOPE-1803
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1803
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 3.0.6
>Reporter: Samuel Garofalo
>Priority: Major
> Fix For: 3.0.7, 4.0.0
>
>
> If a multivalue membership plain schema has only one value and it's deleted 
> from the console, the value is not deleted.



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


[jira] [Commented] (SYNCOPE-1803) Can't remove multivalue membership plain schema value from console

2024-02-19 Thread ASF subversion and git services (Jira)


[ 
https://issues.apache.org/jira/browse/SYNCOPE-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17818443#comment-17818443
 ] 

ASF subversion and git services commented on SYNCOPE-1803:
--

Commit 7925b3216930dd5df558d35609a1066fcc6e6359 in syncope's branch 
refs/heads/3_0_X from Samuel Garofalo
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=7925b32169 ]

[SYNCOPE-1803] Allow removing of all membership plain schemas value from 
console (#622)



> Can't remove multivalue membership plain schema value from console
> --
>
> Key: SYNCOPE-1803
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1803
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 3.0.6
>Reporter: Samuel Garofalo
>Priority: Major
> Fix For: 3.0.7, 4.0.0
>
>
> If a multivalue membership plain schema has only one value and it's deleted 
> from the console, the value is not deleted.



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


Re: [PR] [SYNCOPE-1803] Allow removing of all membership plain schemas value from console [syncope]

2024-02-19 Thread via GitHub


SamuelGaro merged PR #622:
URL: https://github.com/apache/syncope/pull/622


-- 
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