Glad to hear that you solved. Just note that overriding the Spring context classes is not recommended; please have a look to
https://syncope.apache.org/docs/4.0/reference-guide.html#extending-configuration Regards. On 01/09/25 11:02, Lionel SCHWARZ wrote:
Hi Francesco, Thanks, I solved the issue. This problem was that I had overridden "core/src/main/java/org/apache/syncope/core/spring/security/SecurityContext.java" to add the definition of my own JWTSSOProvider in an old 3.0.X syncope version, but forgot to maintain it regarding new syncope versions. I did not noticed the issue before as the core worked perfectly since this time... (I do not really use the console on daily basis) Thanks anyway Regards Lionel ----- Le 30 Aoû 25, à 7:47, Francesco Chicchiriccò <[email protected]> a écrit : So if the "Could not find any registered JWTSSOProvider for issuer ApacheSyncope" error is raised when logging via Console, it is likely that there is something odd going on at Core startup; in particular, either the bean syncopeJWTSSOProvider does not seem to be loaded correctly or the value for the property "security.issuer" was altered. Regards. On 28/08/25 15:05, Lionel SCHWARZ wrote: Hi Francesco, Services seem OK: http://localhost:8080/syncope/rest/keymaster/networkServices/CORE [ { "type": "CORE", "address": "http://localhost:8080/syncope/rest/"; <http://localhost:8080/syncope/rest/> } ] http://localhost:8080/syncope/rest/keymaster/networkServices/CONSOLE [ { "type": "CONSOLE", "address": "http://localhost:8080/syncope-console/"; <http://localhost:8080/syncope-console/> } ] When logging to console I have nothing in core.log and this in console.log: 15:03:00.301 ERROR org.apache.cxf.jaxrs.utils.JAXRSUtils - No message body reader has been found for class org.apache.syncope.common.lib.to.ErrorTO, ContentType: text/html;charset=utf-8 15:03:00.302 ERROR org.apache.cxf.jaxrs.utils.JAXRSUtils - No message body reader has been found for class java.util.List, ContentType: text/html;charset=utf-8 15:03:00.302 ERROR org.apache.syncope.client.console.SyncopeConsoleSession - Authentication failed java.security.AccessControlException: Could not find any registered JWTSSOProvider for issuer ApacheSyncope Regards Lionel ----- Le 28 Aoû 25, à 11:27, Francesco Chicchiriccò <[email protected]> <mailto:[email protected]> a écrit : Hi Lionel, you should ensure that the Console instance is effectively calling the expected Core instance. So, have a look at your Keymaster settings; assuming you are using the Self Keymaster: 1. browse to {syncope-core}/syncope 2. select the Apache Syncope Self Keymaster definition from the top right box 3. authorize as anonymous / <your configured anonymous key> 4. check under Network Services to see if your CONSOLE and CORE instances are correctly reported Naturally, besides this, you could watch your Core and Console logs while attempting to authenticate to Console to see if anything relevant is reported. Regards. On 28/08/25 09:22, Lionel SCHWARZ wrote: Hi Marco, I still have the issue after removing the access token Regards Lionel ----- Le 27 Aoû 25, à 13:42, Marco Di Sabatino Di Diodoro <[email protected]> <mailto:[email protected]> a écrit : Hi Lionel, Remove via rest your access token and try again Regards M Il mar 26 ago 2025, 16:44 Lionel SCHWARZ <[email protected]> ha scritto: Dear all, When trying to login to the console (3.0.11, 3.0.13) with default admin credentials, I get a "Wrong username or password". Login to REST API works fine. Logs output: " 14:12:39.492 ERROR org.apache.syncope.client.console.SyncopeConsoleSession - Authentication failed java.security.AccessControlException: Could not find any registered JWTSSOProvider for issuer ApacheSyncope " although I don't know if this is related to my problem. Does anyone have an idea how to fix this? Regards Lionel
-- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA https://about.me/ilgrosso
