I think i was using BOTH pool connections:
- Application-managed (default); based on HikariCP, the related parameters
can be tuned in the related domain configuration file, e.g.
domains/Master.properties, for the Master domain.
- JavaEE Container-managed, via the JNDI resource matching the
Il 17/10/19 15:09, vesco ha scritto:
Yeah i did follow [1] in facts all files that must be modified:
- provisioning.properties
- domains/Master.properties
Were already ok, i mean i didn't have to edit nothing.
My Postgre version is 12 cause in the reference it's written: "Apache
Syncope 2.1.5
Yeah i did follow [1] in facts all files that must be modified:
- provisioning.properties
- domains/Master.properties
Were already ok, i mean i didn't have to edit nothing.
My Postgre version is 12 cause in the reference it's written: "Apache
Syncope 2.1.5 is verified with PostgreSQL server >=
Hello, thanks for the answer
i did a fresh new VM with the same characteristics as described above.
i had to edit this: /var/lib/pgsql/12/data/pg_hba.conf
and comment this: hostall all 127.0.0.1/32
ident
cause syncope could not connect to the database while
Hi Vesco,
The Quartz tables should be automatically created by Syncope at first
startup. There's no need to import them manually.
The fact that you had to apply this SQL files manually makes me think
about some errors during startup.
I suspect, from the error in core-rest.log, that something
uops ok sorry i've deleted my post and sent another mail
http://syncope-user.1051894.n5.nabble.com/template/NamlServlet.jtp?new_topic
--
Sent from: http://syncope-user.1051894.n5.nabble.com/
Hi,
please send again your e-mail in English, this is a public resource of an
Apache Software Foundation project, and we use that language as common ground
to communicate across the different native languages, thanks.
Regards.
On 10/10/19 15:31, vesco wrote:
> Buongiorno a tutti!
> sto
On 28/12/18 10:52, Suresh Mali wrote:
Brilliant, Many thanks it worked!
Glad to hear this.
BTW just for information this bug is there in 2.0 onwards I guess I
had tried many labels, it is there in 3.0.0-SNAPSHOT as well.
As you can read from SYNCOPE-1406, this bug is originated by
Brilliant, Many thanks it worked! BTW just for information this bug is
there in 2.0 onwards I guess I had tried many labels, it is there in
3.0.0-SNAPSHOT as well. -Suresh
On Friday, December 28, 2018, 2:33:28 PM GMT+5:30, Francesco Chicchiriccò
wrote:
It seems you
It seems you encountered SYNCOPE-1406 [1], whose fix will be delivered
with upcoming Apache Syncope 2.1.3.
Meanwhile, just base your docker-compose on [2] (using 2.1.3-SNAPSHOT as
replacement for ${syncope.version}) and it will work.
Regards.
[1]
Thank you for quick response. Note: both syncope-core rest url,
syncope-enduser urls come properly. Here is the docker-compose file (Only
change I did was changed docker-compose version to '2'
version: '2'
services: db: image: crunchydata/crunchy-postgres:centos7-10.3-1.8.2
Hi,
can you paste somewhere the docker-compose file you are using?
Regards.
On 28/12/18 09:35, Suresh Mali wrote:
Hi,
I am new to syncope, I am trying to install with docker-compose I used
https://syncope.apache.org/docs/getting-started.html#docker-compose-samples
It gets installed,
Hi Maria,
Could you please specify which version of Syncope are you using?
The current implementation of the console shows all other realms, but
disables the ones on which the admin user does not have permission (you
should see a "not allowed" icon on realms different than "Firma1").
in order
On 18/12/2013 23:14, Siva Nookala wrote:
Hi,
In the documentation it is mentioned that the root administrator
(admin) has all the entitlements.
https://cwiki.apache.org/confluence/display/SYNCOPE/Authentication+and+authorization#Authenticationandauthorization-Rootadministrator
When I try to
Hi Francesco,
Thank you for the prompt reply. I am running real-world setup.
Thanks
Siva
On Dec 19, 2013, at 3:23 AM, Francesco Chicchiriccò ilgro...@apache.org wrote:
On 18/12/2013 23:14, Siva Nookala wrote:
Hi,
In the documentation it is mentioned that the root administrator (admin)
On 19/12/2013 14:17, Siva Nookala wrote:
Hi Francesco,
Thank you for the prompt reply. I am running real-world setup.
Ok: some more information requested, then:
* which DBMS?
* which JEE container?
* have you modified core/src/main/resources/content.xml?
* was such role '5' created by
Hi Francesco,Here are the details,Database: mysqlJEE container: tomcatContent.xml is modified to add default roles (attached)The roles I tried to access from syncope console are all created in content.xml. Its fails even after I logout or re-start tomcat.
content.xml
Description: XML document
On
Thank you very much for clearing that up. That did it!!
Thank you very much for your help
Sviva
On Dec 19, 2013, at 8:42 AM, Francesco Chicchiriccò ilgro...@apache.org wrote:
On 19/12/2013 14:33, Siva Nookala wrote:
Hi Francesco,
Here are the details,
Database: mysql
JEE
Thank you very much for clearing that up. That did it!!
Thank you very much for your help
Sviva
On Dec 19, 2013, at 8:42 AM, Francesco Chicchiriccò ilgro...@apache.org wrote:
On 19/12/2013 14:33, Siva Nookala wrote:
Hi Francesco,
Here are the details,
Database: mysql
JEE
19 matches
Mail list logo
