[no subject]
Hello to all users, contributors and Committers! The Travel Assistance Committee (TAC) are pleased to announce that travel assistance applications for Community over Code EU 2024 are now open! We will be supporting Community over Code EU, Bratislava, Slovakia, June 3th - 5th, 2024. TAC exists to help those that would like to attend Community over Code events, but are unable to do so for financial reasons. For more info on this years applications and qualifying criteria, please visit the TAC website at < https://tac.apache.org/ >. Applications are already open on https://tac-apply.apache.org/, so don't delay! The Apache Travel Assistance Committee will only be accepting applications from those people that are able to attend the full event. Important: Applications close on Friday, March 1st, 2024. Applicants have until the the closing date above to submit their applications (which should contain as much supporting material as required to efficiently and accurately process their request), this will enable TAC to announce successful applications shortly afterwards. As usual, TAC expects to deal with a range of applications from a diverse range of backgrounds; therefore, we encourage (as always) anyone thinking about sending in an application to do so ASAP. For those that will need a Visa to enter the Country - we advise you apply now so that you have enough time in case of interview delays. So do not wait until you know if you have been accepted or not. We look forward to greeting many of you in Bratislava, Slovakia in June, 2024! Kind Regards, Gavin (On behalf of the Travel Assistance Committee)
[no subject]
Hi, I wanted to ask if Syncope is / can be used to store linux group ID's . We have some users and groups in Azure AD and I would like to have available for linux systems - sync those users and groups - generate the grup GID for linux (integer in high range - 9000 - 3) - generate the UID for linux ( integer in high range - 9000 - 3) - generate the linux group name ?! - generate the linux user name (first part of email ?! ) - periodically sync the groups and users to all linux hosts - there is a project for this already that integrates with linux https://github.com/google/nsscache Has anyone done something similar with Syncope? Syncope seems to have most of the bits we need for this job. (edited) Is there a better way of handling this? -- Eugen
[no subject]
Hi, FYI, I am a colleague of Noah and have been "trying" to help get this new Syncope installation working, so I'd like to add some notes to the error/stack trace that he posted: - FYI, the Tomcat instance itself seems to work, e.g., I can go to http://hostname:8080/ and get a web page, and also the manage app web page (http://hostname:8080/manager/html works and I can log into that. - That error/stacktrace that he posted is from trying to access http://hostname:8080/syncope-console/. - Can someone let us know how we might be able to enable some debug logging to try to determine what is wrong? FYI, we have checked logging under /apps/apache-tomcat/logs, and under /apps/syncope/logs and /apps/syncope-archetype/logs. The latter dir has nothing in it. The /apps/syncope/logs has only enduser.log vs. on the older Syncope instance that works, there is a enduser.log and a console.log. Thanks! Jim On Thursday, July 18, 2019, 5:07:50 PM UTC, Noah wrote: Hi All, I’m attempting to install Syncope 2.1.4 and I’m running into the error posted below. I’m using: Maven 3.6.1 Tomcat 9.0.21 MySQL 8.0.16 MySQL Java Connector 8.0.16 Here is the error: org.apache.wicket.WicketRuntimeException: Unable to instantiate web session class org.apache.syncope.client.console.SyncopeConsoleSession org.apache.wicket.authroles.authentication.AuthenticatedWebApplication.newSession(AuthenticatedWebApplication.java:121) org.apache.wicket.Application.fetchCreateAndSetSession(Application.java:1555) org.apache.wicket.Session.get(Session.java:176) org.apache.syncope.client.console.SyncopeConsoleSession.get(SyncopeConsoleSession.java:91) org.apache.syncope.client.console.SyncopeConsoleRequestCycleListener.onException(SyncopeConsoleRequestCycleListener.java:80) org.apache.wicket.request.cycle.RequestCycleListenerCollection$4.notify(RequestCycleListenerCollection.java:126) org.apache.wicket.request.cycle.RequestCycleListenerCollection$4.notify(RequestCycleListenerCollection.java:122) org.apache.wicket.util.listener.ListenerCollection.notify(ListenerCollection.java:80) org.apache.wicket.request.cycle.RequestCycleListenerCollection.onException(RequestCycleListenerCollection.java:121) org.apache.wicket.request.cycle.RequestCycleListenerCollection$4.notify(RequestCycleListenerCollection.java:126) org.apache.wicket.request.cycle.RequestCycleListenerCollection$4.notify(RequestCycleListenerCollection.java:122) org.apache.wicket.util.listener.ListenerCollection.notify(ListenerCollection.java:80) org.apache.wicket.request.cycle.RequestCycleListenerCollection.onException(RequestCycleListenerCollection.java:121) org.apache.wicket.request.cycle.RequestCycle.handleException(RequestCycle.java:368) org.apache.wicket.request.cycle.RequestCycle.executeExceptionRequestHandler(RequestCycle.java:314) org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:259) org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:221) org.apache.wicket.protocol.ws.AbstractUpgradeFilter.processRequestCycle(AbstractUpgradeFilter.java:70) org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:206) org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:299) Root Cause java.lang.reflect.InvocationTargetException sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) java.lang.reflect.Constructor.newInstance(Constructor.java:423) org.apache.wicket.authroles.authentication.AuthenticatedWebApplication.newSession(AuthenticatedWebApplication.java:117) org.apache.wicket.Application.fetchCreateAndSetSession(Application.java:1555) org.apache.wicket.Session.get(Session.java:176) org.apache.syncope.client.console.SyncopeConsoleSession.get(SyncopeConsoleSession.java:91) org.apache.syncope.client.console.SyncopeConsoleRequestCycleListener.onException(SyncopeConsoleRequestCycleListener.java:80) org.apache.wicket.request.cycle.RequestCycleListenerCollection$4.notify(RequestCycleListenerCollection.java:126) org.apache.wicket.request.cycle.RequestCycleListenerCollection$4.notify(RequestCycleListenerCollection.java:122) org.apache.wicket.util.listener.ListenerCollection.notify(ListenerCollection.java:80) org.apache.wicket.request.cycle.RequestCycleListenerCollection.onException(RequestCycleListenerCollection.java:121)
[no subject]
Hi All, I’m attempting to install Syncope 2.1.4 and I’m running into the error posted below. I’m using: Maven 3.6.1 Tomcat 9.0.21 MySQL 8.0.16 MySQL Java Connector 8.0.16 Here is the error: org.apache.wicket.WicketRuntimeException: Unable to instantiate web session class org.apache.syncope.client.console.SyncopeConsoleSession org.apache.wicket.authroles.authentication.AuthenticatedWebApplication.newSession(AuthenticatedWebApplication.java:121) org.apache.wicket.Application.fetchCreateAndSetSession(Application.java:1555) org.apache.wicket.Session.get(Session.java:176) org.apache.syncope.client.console.SyncopeConsoleSession.get(SyncopeConsoleSession.java:91) org.apache.syncope.client.console.SyncopeConsoleRequestCycleListener.onException(SyncopeConsoleRequestCycleListener.java:80) org.apache.wicket.request.cycle.RequestCycleListenerCollection$4.notify(RequestCycleListenerCollection.java:126) org.apache.wicket.request.cycle.RequestCycleListenerCollection$4.notify(RequestCycleListenerCollection.java:122) org.apache.wicket.util.listener.ListenerCollection.notify(ListenerCollection.java:80) org.apache.wicket.request.cycle.RequestCycleListenerCollection.onException(RequestCycleListenerCollection.java:121) org.apache.wicket.request.cycle.RequestCycleListenerCollection$4.notify(RequestCycleListenerCollection.java:126) org.apache.wicket.request.cycle.RequestCycleListenerCollection$4.notify(RequestCycleListenerCollection.java:122) org.apache.wicket.util.listener.ListenerCollection.notify(ListenerCollection.java:80) org.apache.wicket.request.cycle.RequestCycleListenerCollection.onException(RequestCycleListenerCollection.java:121) org.apache.wicket.request.cycle.RequestCycle.handleException(RequestCycle.java:368) org.apache.wicket.request.cycle.RequestCycle.executeExceptionRequestHandler(RequestCycle.java:314) org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:259) org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:221) org.apache.wicket.protocol.ws.AbstractUpgradeFilter.processRequestCycle(AbstractUpgradeFilter.java:70) org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:206) org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:299) Root Cause java.lang.reflect.InvocationTargetException sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) java.lang.reflect.Constructor.newInstance(Constructor.java:423) org.apache.wicket.authroles.authentication.AuthenticatedWebApplication.newSession(AuthenticatedWebApplication.java:117) org.apache.wicket.Application.fetchCreateAndSetSession(Application.java:1555) org.apache.wicket.Session.get(Session.java:176) org.apache.syncope.client.console.SyncopeConsoleSession.get(SyncopeConsoleSession.java:91) org.apache.syncope.client.console.SyncopeConsoleRequestCycleListener.onException(SyncopeConsoleRequestCycleListener.java:80) org.apache.wicket.request.cycle.RequestCycleListenerCollection$4.notify(RequestCycleListenerCollection.java:126) org.apache.wicket.request.cycle.RequestCycleListenerCollection$4.notify(RequestCycleListenerCollection.java:122) org.apache.wicket.util.listener.ListenerCollection.notify(ListenerCollection.java:80) org.apache.wicket.request.cycle.RequestCycleListenerCollection.onException(RequestCycleListenerCollection.java:121) org.apache.wicket.request.cycle.RequestCycleListenerCollection$4.notify(RequestCycleListenerCollection.java:126) org.apache.wicket.request.cycle.RequestCycleListenerCollection$4.notify(RequestCycleListenerCollection.java:122) org.apache.wicket.util.listener.ListenerCollection.notify(ListenerCollection.java:80) org.apache.wicket.request.cycle.RequestCycleListenerCollection.onException(RequestCycleListenerCollection.java:121) org.apache.wicket.request.cycle.RequestCycle.handleException(RequestCycle.java:368) org.apache.wicket.request.cycle.RequestCycle.executeExceptionRequestHandler(RequestCycle.java:314) org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:259) org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:221) org.apache.wicket.protocol.ws.AbstractUpgradeFilter.processRequestCycle(AbstractUpgradeFilter.java:70) org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:206)
[no subject]
I downloaded and ran syncope-standalone-2.0.8-distribution.zip. The app starts up and I am able to get into the application as an admin. However, after I create a new user and then try to set their password, I get the error below about the EMAIL column not existing in the user table. Looking in $TOMCAT_HOME/webapps/syncope-fit-build-tools/WEB-INF/classes/testdb.sql, I see the definition for the user table and it is indeed missing an email column. Am I doing something wrong or is that a known issue? Thanks Andrew 09:55:31.972 ERROR net.tirasa.connid.bundles.soap.provisioning.interfaces.Provisioning - Search operation failed org.h2.jdbc.JdbcSQLException: Column "EMAIL" not found; SQL statement: SELECT * FROM user WHERE email='myn...@gmail.com' [42122-196] at org.h2.engine.SessionRemote.done(SessionRemote.java:629) ~[h2-1.4.196.jar:1.4.196] at org.h2.command.CommandRemote.prepare(CommandRemote.java:83) ~[h2-1.4.196.jar:1.4.196] at org.h2.command.CommandRemote.(CommandRemote.java:49) ~[h2-1.4.196.jar:1.4.196] at org.h2.engine.SessionRemote.prepareCommand(SessionRemote.java:499) ~[h2-1.4.196.jar:1.4.196] at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1204) ~[h2-1.4.196.jar:1.4.196] at org.h2.jdbc.JdbcStatement.executeQuery(JdbcStatement.java:73) ~[h2-1.4.196.jar:1.4.196] at org.apache.syncope.fit.buildtools.cxf.ProvisioningImpl.query(ProvisioningImpl.java:205) [classes/:?]
[no subject]
Hi Sergio,
could please add the "SakaiUserSearchScript.groovy" too?
I need to see whether the "eid" field is set correctly and does always return a
value that will be mapped to "username".
Regards,
Matteo
On 2017-09-14 18:20, Sergio Muriel <sergio...@hotmail.com> wrote:
> Hi Matteo,
>
> please find the screenshots attached to this email.
>
>
> Thank you in advance!
>
>
> PD: If is not pictured then values are by default.
>
> Best Regards,
> Sergio Muriel
>
>
>
> From: Matteo Alessandroni <matteo.alessandr...@tirasa.net>
> Sent: Thursday, September 14, 2017 2:23 AM
> To: user@syncope.apache.org
> Subject: Re: Scripted SQL Pull Task Error
>
> Hi Sergio,
>
> At this point could you please attach a screenshot of your mapping and also
> the Connector and Resource configuration?
>
> Regards,
> Matteo
>
> On 14/09/2017 00:02, Sergio Muriel wrote:
>
> Hi Matteo,
>
> * "username" is mapped in my resource. The "Purpose" column for
> "username" is set to the icon with both pull and push arrows. (That is Sync,
> I believe).
> * All users have a valid non blank username value. Indeed, I checked with
> a query, and it has been checked also by Sakai itself.
>
> So far I have the same problem. This is what the logs say:
>
> core-persistence.log shows this for each user creation attempt:
> 16:29:19.947 WARN
> org.apache.syncope.core.persistence.jpa.validation.entity.EntityValidationListener
> - Bean validation errors found:
> [ConstraintViolationImpl{rootBean=JPAUser[null], propertyPath='username',
> message='Blank username', leafBean=JPAUser[null], value=null}]
>
>
> core.log shows this for each user creation attempt:
> 16:26:28.884 ERROR
> org.apache.syncope.core.provisioning.api.pushpull.SyncopeResultHandler -
> Could not create USER f84440b0-3cc7-4d83-ae02-951c81faf2e22
> org.apache.syncope.core.persistence.api.attrvalue.validation.InvalidEntityException:
> JPAUser [Standard]
> at
> org.apache.syncope.core.persistence.jpa.validation.entity.EntityValidationListener.validate(EntityValidationListener.java:73)
> ~[syncope-core-persistence-jpa-2.0.4.jar:2.0.4]
> at sun.reflect.GeneratedMethodAccessor517.invoke(Unknown Source) ~[?:?]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> ~[?:1.8.0_71]
> at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.8.0_71]
> at
> org.apache.openjpa.event.BeanLifecycleCallbacks.makeCallback(BeanLifecycleCallbacks.java:85)
> ~[openjpa-kernel-2.4.2.jar:2.4.2]
> at
> org.apache.openjpa.persistence.PersistenceListenerAdapter.makeCallback(PersistenceListenerAdapter.java:71)
> ~[openjpa-persistence-2.4.2.jar:2.4.2]
> at
> org.apache.openjpa.persistence.PersistenceListenerAdapter.beforePersist(PersistenceListenerAdapter.java:85)
> ~[openjpa-persistence-2.4.2.jar:2.4.2]
> at
> org.apache.openjpa.event.LifecycleEventManager.fireEvent(LifecycleEventManager.java:404)
> ~[openjpa-kernel-2.4.2.jar:2.4.2]
> at
> org.apache.openjpa.event.LifecycleEventManager.fireEvent(LifecycleEventManager.java:308)
> ~[openjpa-kernel-2.4.2.jar:2.4.2]
> at
> org.apache.openjpa.kernel.BrokerImpl.fireLifecycleEvent(BrokerImpl.java:814)
> ~[openjpa-kernel-2.4.2.jar:2.4.2]
> at
> org.apache.openjpa.kernel.VersionAttachStrategy.attach(VersionAttachStrategy.java:140)
> ~[openjpa-kernel-2.4.2.jar:2.4.2]
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:252)
> ~[openjpa-kernel-2.4.2.jar:2.4.2]
> at org.apache.openjpa.kernel.AttachManager.attach(AttachManager.java:105)
> ~[openjpa-kernel-2.4.2.jar:2.4.2]
> at org.apache.openjpa.kernel.BrokerImpl.attach(BrokerImpl.java:3508)
> ~[openjpa-kernel-2.4.2.jar:2.4.2]
> at
> org.apache.openjpa.kernel.DelegatingBroker.attach(DelegatingBroker.java:1213)
> ~[openjpa-kernel-2.4.2.jar:2.4.2]
> at
> org.apache.openjpa.persistence.EntityManagerImpl.merge(EntityManagerImpl.java:879)
> ~[openjpa-persistence-2.4.2.jar:2.4.2]
> at
> org.apache.syncope.core.persistence.jpa.dao.AbstractAnyDAO.save(AbstractAnyDAO.java:543)
> ~[syncope-core-persistence-jpa-2.0.4.jar:2.0.4]
> at
> org.apache.syncope.core.persistence.jpa.dao.JPAUserDAO.save(JPAUserDAO.java:437)
> ~[syncope-core-persistence-jpa-2.0.4.jar:2.0.4]
> at
> org.apache.syncope.core.persistence.jpa.dao.JPAUserDAO.save(JPAUserDAO.java:84)
> ~[syncope-core-persistence-jpa-2.0.4.jar:2.0.4]
> at sun.reflect.GeneratedMethodAccessor527.invoke(Unknown Source) ~[?:?]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> ~[?:1.8.0_71]
> at java.lang.
Re: UserTo subject in SyncActions
Hi, Il 26/03/2015 15:12, Manfredo Hopp ha scritto: Marco now this is really helpful since [1] doesnt say anything about this I replied with a yes. I don't understand what's your problem. On the other hand I would like to know where I stated the same question in order to avoid making same mistake in the future. Thanks! This thread is similar to the Memberships thread. I want to help you, but the information about your problems are always insufficient to give a complete answer. M 2015-03-26 5:31 GMT-03:00 Marco Di Sabatino Di Diodoro marco.disabat...@tirasa.net mailto:marco.disabat...@tirasa.net: Hi Manfredo Il 25/03/2015 22:27, Manfredo Hopp ha scritto: Hi, I would like to know if modifying subject of type userTO in a SycAction class will update corresponding SyncopeUser Yes. A SycAction is a Java class that implements some specific actions to be performed before and after synchronization [1]. If you're working with beforeProvision/beforeAssign you need to manipulate the UserTO, otherwise if the user is already present on Syncope (beforeUpdate) you need to work with the UserMod. Please don't open new thread for the same question. Thanks Marco [1] https://cwiki.apache.org/confluence/display/SYNCOPE/SyncActionsClass Thanks -- Dott. Marco Di Sabatino Di Diodoro Tel. +39 3939065570 Tirasa S.r.l. Viale D'Annunzio 267 - 65127 Pescara Tel +39 0859116307 / FAX +39 085973 http://www.tirasa.net Apache Syncope PMC Member http://people.apache.org/~mdisabatino/ http://people.apache.org/%7Emdisabatino/ -- Dott. Marco Di Sabatino Di Diodoro Tel. +39 3939065570 Tirasa S.r.l. Viale D'Annunzio 267 - 65127 Pescara Tel +39 0859116307 / FAX +39 085973 http://www.tirasa.net Apache Syncope PMC Member http://people.apache.org/~mdisabatino/
Re: UserTo subject in SyncActions
Marco now this is really helpful since [1] doesnt say anything about this! On the other hand I would like to know where I stated the same question in order to avoid making same mistake in the future. Thanks! 2015-03-26 5:31 GMT-03:00 Marco Di Sabatino Di Diodoro marco.disabat...@tirasa.net: Hi Manfredo Il 25/03/2015 22:27, Manfredo Hopp ha scritto: Hi, I would like to know if modifying subject of type userTO in a SycAction class will update corresponding SyncopeUser Yes. A SycAction is a Java class that implements some specific actions to be performed before and after synchronization [1]. If you're working with beforeProvision/beforeAssign you need to manipulate the UserTO, otherwise if the user is already present on Syncope (beforeUpdate) you need to work with the UserMod. Please don't open new thread for the same question. Thanks Marco [1] https://cwiki.apache.org/confluence/display/SYNCOPE/SyncActionsClass Thanks -- Dott. Marco Di Sabatino Di Diodoro Tel. +39 3939065570 Tirasa S.r.l. Viale D'Annunzio 267 - 65127 Pescara Tel +39 0859116307 / FAX +39 085973http://www.tirasa.net Apache Syncope PMC Memberhttp://people.apache.org/~mdisabatino/
UserTo subject in SyncActions
Hi, I would like to know if modifying subject of type userTO in a SycAction class will update corresponding SyncopeUser Thanks
