Taking this as an example: ~~~ http://localhost:8090/rest/history/example ~~~ 1. Clone the git repo ~~~ $ git clone https://github.com/agiertli/realtime-jms-audit-replication.git ~~~ 2. Checkout 'fix-swagger' branch ~~~ $ cd realtime-jms-audit-replication $ git checkout fix-swagger ~~~ 3. Go to "realtime-jms-audit-replication/kjar" deploy ~~~ $ mvn clean install ~~~ 4. Go to "realtime-jms-audit-replication/spring-boot-kie-server" run ~~~ $ mvn spring-boot:run -Dspring-boot.run.profiles=local ~~~ When you call ~~~ $ curl --user anton:password1! http://localhost:8090/rest/swagger.json ~~~ instead of actual swagger doc, you receive an example response, see: ~~~ { "swagger": "2.0", "info": { "description": "The Application", "version": "1.0.0", "title": "Sample REST Application", "contact": { "name": "users@cxf.apache.org" } , "license": { "name": "Apache 2.0 License", "url": "http://www.apache.org/licenses/LICENSE-2.0.html" } }, "basePath": "/rest" } ~~~ If the cxf.jaxrs.classes-scan and cxf.jaxrs.classes-scan-packages properties from properties file are commented, then the swagger doc is generated, however the custom endpoint no longer works and the generated swagger doc does not contain our endpoint. If you need credentials, you can use any of these: ~~~ user / user -> roles: kie-server wbadmin / wbadmin -> roles: admin kieserver / kieserver1! -> roles: kie-server anton / password1! -> roles: kie-server,admin,rest-all ~~~