Hi,
OK, so that was the logic behind it! Now I start to have all the dependencies
clear. Tested it and now everything makes sense.
Our deployment is pretty small though. Only 200 + personnel + some 2000
students. But I’ll check the postgress option. The core seems to be configured
by default towards the Postgress option.
I like the way you can augment Syncope if needed in a strongly typed language.
Maybe we’ll even be able to remove the existing php-based “IDM”, which is more
of a plain sync engine with no editable business logic capabilities what so
ever. Not my production though…
It might be that we will end up with a *nix environment in the end.
Thanks a lot!
Regards,
Mikael
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: tiistai 28. helmikuuta 2017 17.54
To: user@syncope.apache.org
Subject: Re: Creating a virtual schema type ->empty type list
On 28/02/2017 16:26, Mikael Ekblom wrote:
Hi,
We are currently evaluating Syncopy as a candidate for our future IDM.
Hi,
glad to hear that :-)
We have some choices on the table and we are even considering writing our own
IDM from scratch, but that is something I would like to avoid for practical
reasons…☺ I think that would be inventing the wheel again nowadays. Our
neighbor Helsinki University is implementing the same solution, so I thought
that I will join the community regarding this one.
Anyhow, I have a working Syncopy 2.0.2 running on a Windows server 2012 R2 with
mysql as the backbone. It is setup and configured via Apache Maven and is
running with Tomcat 8.5 as the container. Everything seems to be working.
I have managed to create the connector to our AD with the built in/shipped
connector. I have also assigned a resource to that connector. Via that
resource, we will pull information from our AD as an initial test. The
connector reports that it works.
Very nice, indeed.
One note: while it is perfectly fine for evaluation, I would personally prefer
PostgreSQL over MySQL / MariaDB, as some of my customers have been reporting
complaints about search performances.
We have been constantly providing enhancements and fixes about that, but there
have been simply no issues in all the PostgreSQL-based deployments - some of
them being very large in numbers.
One problem though. I have been able to create all schema types but the virtual
one. When I’m supposed to create a virtual schema type for attributes that
Syncope will not own and set the ad-resource as the de facto resource, the
type drop down list for the virtual schema is empty and just states “Choose
one”.
What am I missing here? Some schema definition topic missed somewhere? This is
not a panic question, as we are just evaluating, but I figure that I might save
some time to ask via the mailing list first. I do have my own abstractions to
do for our own maybe to come IDM…☺
I am assuming you are using the Admin UI here.
If so, you need first to select a Resource (among the ones available) and then
the Type combo will be populated with all the provision rules defined for that
Resource.
Finally, you will need to provide the external attribute to which the new
Virtual Schema's attributes will be linked.
More details available at:
https://syncope.apache.org/docs/reference-guide.html#virtual
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/
