Hi,
I saw the announcements this morning about 2.1.6 and 2.0.15. Are you all
simultaneously supporting two different branches/versions of Syncope?
Or are 2.1.6 and 2.0.15 different "products"?
Thanks,
Jim
Hi,
I was looking at the ItemTransformer
(https://syncope.apache.org/apidocs/2.0/org/apache/syncope/core/provisioning/api/data/ItemTransformer.html)
but it looks that is applied to/bound to an individual attribute, and returns
the transformed attribute value, but in my use case, I want to
Hi,
I can accept that and move on :)...
FYI, the reason that I was aware of, and was able to find the Javadocs is that,
as you probably know, we have already worked with, and have several,
ItemTransformers. And that was also the reason that led me to that dead end
(because they only return
Hi,
Thanks. I did read that information and also some information that we had
gathered by another person, but you know, it is not easy to comprehend some of
the Syncope functionality/concepts via just the documentation, and mind you, I
have been doing this kind of work for a long time with
Hi,
I was wondering if maybe derived attributes could be another approach that
might work. I was reading this:
http://commons.apache.org/proper/commons-jexl/
and noted this:
"Support for invocation of any accessible method (see example above).
Support for setting/getting any accessible
Hi,
I wanted to test pull actions, so I am trying to build and deploy the
LDAPPasswordPullActions example:
https://github.com/apache/syncope/blob/syncope-2.1.5/core/provisioning-java/src/main/java/org/apache/syncope/core/provisioning/java/pushpull/LDAPPasswordPullActions.java
I was able
Hi,
For the scenario that I described (I have a pull task that is pulling an
attribute from an LDAP user into the realm, and I want to process the value of
that attribute and populate 2 other attributes
that are the results of the processing), how does my code in the pull action
class access
Hi,
Actually, I was just looking at the original
syncope-core-provisioning-java-2.1.5.jar and that has a class with the same
name in the same directory inside the JAR. I'm assuming that was because you
all include that when we built Syncope.
So when I did what I did, I basically just
Hi,
FYI, I put the original syncope-core-provisioning-java-2.1.5.jar back and
bounced the Tomcat, and the pull action is still not appearing in the console.
Jim
On Monday, May 4, 2020, 03:02:40 AM EDT, wrote:
Hi,
Actually, I was just looking at the original
Hi,
No.
I was able to build the LDAPPasswordPullActions.java separately, in Eclipse,
using JARs from the Syncope installation. That got me the
LDAPPasswordPullActions.class file in
./org/apache/syncope/core/provisioning/java/pushpull/LDAPPasswordPullActions.class.
Then, I ran:
jar uf
Hi,
Can someone here answer my question below re. PULL Action class:
"how does my code in the pull action class access the attribute that was pulled
and how does it store the resulting 2 attribute values into the realm"
??
Thanks,
Jim
On Saturday, May 2, 2020, 04:59:09 PM EDT, wrote:
Hi,
I was able to build and deploy the LDAPPasswordPullActions pull action to one
of our 2.1.5 Syncope instances and am trying to test it. I assume that this
normally takes in the LDAP userPassword attribute, but I was wondering what the
"Type" of the "userPassword" attribute should be in the
Hi,
In the after() method of a Pull Actions, I am trying to list out the user
attributes from the pull, e.g.:
User myUser = userDAO.find(entity.getKey());
List listOfAttrs = outsideUser.getPlainAttrs();
// Print the name from the list
Hi,
I have been continuing to work on implementing a pull action that I've
described in previous messages, but I am not sure how to set the attributes
that I want the pull action to output TO? Can someone explain how to do that?
Thanks,
Jim
Hi,
I have been able to configure an Apache proxy in front of Syncope
(/syncope-console) running under Tomcat. I am using mod_ajp to connect the
Apache to the Tomcat that Syncope is running under and I configured an AJP
connector on that Tomcat. Also, I am able to pass a logged-in user
before getting into Syncope configurations.
Regards.
On 17/05/20 11:34, ohaya wrote:
> Hi,
>
> I have been able to configure an Apache proxy in front of Syncope
> (/syncope-console) running under Tomcat. I am using mod_ajp to connect the
> Apache to the Tomcat that Syncope
I noted that the OIDC article that you linked was from 2018, so it seems that
that configuration should be available in Syncope 2.1.5?
Jim
On Monday, May 18, 2020, 06:12:40 AM EDT, ohaya wrote:
Hi Francesco,
Ah. Thanks.
We potentially might be able to leverage either
Ahh! I just noticed from Section 3.17 of the Syncope reference guide that we
need to include those extensions during our Syncope build. I will check on
doing that or having that done.
Jim
On Monday, May 18, 2020, 06:18:58 AM EDT, ohaya wrote:
I noted that the OIDC article
On Monday, May 18, 2020, 06:18:58 AM EDT, ohaya wrote:
I noted that the OIDC article that you linked was from 2018, so it seems that
that configuration should be available in Syncope 2.1.5?
Jim
On Monday, May 18, 2020, 06:12:40 AM EDT, ohaya wrote:
Hi Francesco,
Ah
FYI, that line is getting truncated at 64 characters...
Jim
On Tuesday, May 5, 2020, 05:36:41 PM EDT, wrote:
Hi,
We have the following code in the after() method to save information to an
attribute, but we are getting errors shown below when we try to save.
FYI, we do have that
Hi,
We have the following code in the after() method to save information to an
attribute, but we are getting errors shown below when we try to save.
FYI, we do have that attribute enabled for "unique", which I guess MAY be
causing that "Duplicate entry" error, but if that is the case, does
Hi,
Oops, I forgot to include the code snippet that I was referring to:
// Store the 'SubjectString' value into the 'CertSubjectString' attrib in
Syncope realm...
UPlainAttr attr4Cert = entityFactory.newEntity(UPlainAttr.class);
attr4Cert.setOwner(outsideUser);
Best doc is this:
http://syncope.apache.org/rest/2.1/index.html
you can click around to expand and includes the params, etc.
Jim
On Monday, May 18, 2020, 10:36:07 AM EDT, syncope developer
wrote:
Wanted to look at the REST Api calls for manipulating the provision mapping
alone -
Hi,
I just found these msgs in the syncope-archetype/logs/enduser.log:
14:17:04.128 ERROR org.apache.syncope.client.enduser.resources.BaseResource -
XSRF TOKEN does not match
I am guessing that XSRF is something to do with cross-site? Is there some
config we have to change in Syncope to
I found xsrf and catcha parameters in the
/syncope-archetype/enduser/target/classes/enduser.properties file, and I set
both parameters to "false", and bounced the tomcat, but still it is getting
stuck.
I am also now still seeing the following error in the enduser.log:
18:27:38.717 ERROR
Ok, I was missing a configuration in server.xml... it is working now.
On Thursday, May 14, 2020, 03:15:44 PM EDT, wrote:
Also in the Tomcat localhost log file I am seeing this:
192.168.181.153 - - [14/May/2020:18:41:33 +] "POST
Also in the Tomcat localhost log file I am seeing this:
192.168.181.153 - - [14/May/2020:18:41:33 +] "POST
/syncope-console/login;jsessionid=145679823C04C8CB87203E692507C264?0-1.0-login-submit
HTTP/1.1" 400 1186
I think that is a 400 error, but I am not sure "why?" because I am not seeing
Hi,
I am trying to proxy the Syncope console with an Apache (reverse) proxy.
So far, after I setup the Apache proxy, I can get to the Syncope console login
page, but when I try to submit the login, nothing happens.
I have been trying to diagnose what is going on, but so far, I cannot see
28 matches
Mail list logo
