-
Notifications
You must be signed in to change notification settings - Fork 17
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
104 changed files
with
2,904 additions
and
1,820 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,26 @@ | ||
| name: CI | ||
| 'on': | ||
| push: | ||
| branches: | ||
| - develop | ||
| pull_request: | ||
| branches: | ||
| - develop | ||
| jobs: | ||
| unit-test: | ||
| name: Unit Tests | ||
| runs-on: ubuntu-latest | ||
| steps: | ||
| - name: Git checkout | ||
| uses: actions/checkout@v2 | ||
| - name: Use Java 8 | ||
| uses: actions/setup-java@v1 | ||
| with: | ||
| java-version: 8 | ||
| - name: 'Unit Tests with Java 8' | ||
| run: | | ||
| mvn install -DskipTests=true -Dmaven.javadoc.skip=true -B -V | ||
| mvn test -B | ||
| env: | ||
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
| COVERALLS_TOKEN: ${{ secrets.COVERALLS_TOKEN }} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -4,3 +4,5 @@ | |
| /.README.md.html | ||
| /.CHANGELOG.md.html | ||
| /.pmd | ||
| /.idea | ||
| *.iml | ||
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,59 +1,59 @@ | ||
| ## AuthzForce Server CE - Minimal Docker image | ||
|
|
||
| This image of a minimal AuthzForce Server runtime is intended to work together with [Identity Manager - Keyrock](http://catalogue.fiware.org/enablers/identity-management-keyrock) and [PEP Proxy Wilma](http://catalogue.fiware.org/enablers/pep-proxy-wilma) generic enabler. | ||
|
|
||
| ## Image contents | ||
| - OpenJDK JRE 8; | ||
| - Tomcat 9; | ||
| - AuthzForce Server CE (version matching the Docker image tag). | ||
|
|
||
| ## Usage | ||
|
|
||
| This image gives you a minimal installation for testing purposes. The AuthzForce Installation and Administration guide on [readthedocs.org](https://readthedocs.org/projects/authzforce-ce-fiware/versions/) (select the version matching the Docker image tag, then **AuthzForce - Installation and Administration Guide**) provides you a better approach for using it in a production environment. This installation guide also gives instructions to install from .deb package (instead of Docker), which is the recommended way for Ubuntu hosts. | ||
|
|
||
| Create a container using `authzforce/server` image by doing (replace the first *8080* after *-p* with whatever network port you want to use on the host to access the AuthzForce Server, e.g. 80; and *release-9.0.0* with the current Docker image tag that you are using): | ||
|
|
||
| ``` | ||
| docker run -d -p 8080:8080 --name <container-name> fiware/authzforce-ce-server:release-9.0.0 | ||
| ``` | ||
|
|
||
| As stands in the AuthzForce Installation and administration guide on [readthedocs.org](https://readthedocs.org/projects/authzforce-ce-fiware/versions/) (select the version matching the Docker image tag, then **AuthzForce - Installation and Administration Guide**) you can: | ||
|
|
||
| * **Create a domain** | ||
|
|
||
| ``` | ||
| curl -s --request POST \ | ||
| --header "Accept: application/xml" \ | ||
| --header "Content-Type: application/xml;charset=UTF-8" \ | ||
| --data '<?xml version="1.0" encoding="UTF-8"?><taz:domainProperties xmlns:taz="http://authzforce.github.io/rest-api-model/xmlns/authz/5" />' \ | ||
| http://<authzforce-container-ip>:8080/authzforce-ce/domains | ||
| ``` | ||
|
|
||
| * **Retrieve the domain ID** | ||
|
|
||
| ``` | ||
| curl -s --request GET http://<authzforce-container-ip>:8080/authzforce-ce/domains | ||
| ``` | ||
|
|
||
| * **Domain removal** | ||
|
|
||
| ``` | ||
| curl --verbose --request DELETE \ | ||
| --header "Content-Type: application/xml;charset=UTF-8" \ | ||
| --header "Accept: application/xml" \ | ||
| http://<authzforce-container-ip>:8080/authzforce-ce/domains/<domain-id> | ||
| ``` | ||
|
|
||
| * **User and Role Management Setup && Domain Role Assignment** | ||
|
|
||
| These tasks are now delegated to the [Identity Manager - Keyrock](http://catalogue.fiware.org/enablers/identity-management-keyrock) enabler. Here you can find how to use the interface for that purpose: [How to manage AuthzForce in Fiware](https://www.fiware.org/devguides/handling-authorization-and-access-control-to-apis/how-to-manage-access-control-in-fiware/). | ||
|
|
||
| ## User feedback | ||
|
|
||
| ### Documentation | ||
|
|
||
| All the information regarding the Dockerfile is hosted publicly on [Github](https://github.com/authzforce/server/tree/master/src/docker). | ||
|
|
||
| ### Issues | ||
|
|
||
| If you find any issue with this image, feel free to report at [Github issue tracking system](https://github.com/authzforce/server/issues). | ||
| ## AuthzForce Server CE - Minimal Docker image | ||
|
|
||
| This image of a minimal AuthzForce Server runtime is intended to work together with [Identity Manager - Keyrock](http://catalogue.fiware.org/enablers/identity-management-keyrock) and [PEP Proxy Wilma](http://catalogue.fiware.org/enablers/pep-proxy-wilma) generic enabler. | ||
|
|
||
| ## Image contents | ||
| - OpenJDK JRE 8; | ||
| - Tomcat 9 (since AuthzForce Server v9.0.1, else Tomcat 8 for older versions); | ||
| - AuthzForce Server CE (version matching the Docker image tag). | ||
|
|
||
| ## Usage | ||
|
|
||
| This image gives you a minimal installation for testing purposes. The AuthzForce Installation and Administration guide on [readthedocs.org](https://readthedocs.org/projects/authzforce-ce-fiware/versions/) (select the version matching the Docker image tag, then **AuthzForce - Installation and Administration Guide**) provides you a better approach for using it in a production environment. This installation guide also gives instructions to install from .deb package (instead of Docker), which is the recommended way for Ubuntu hosts. | ||
|
|
||
| Create a container using `authzforce/server` image by doing (replace the first *8080* after *-p* with whatever network port you want to use on the host to access the AuthzForce Server, e.g. 80; and *release-9.0.1* with the current Docker image tag that you are using): | ||
|
|
||
| ``` | ||
| docker run -d -p 8080:8080 --name <container-name> authzforce/server:release-9.0.1 | ||
| ``` | ||
|
|
||
| As stands in the AuthzForce Installation and administration guide on [readthedocs.org](https://readthedocs.org/projects/authzforce-ce-fiware/versions/) (select the version matching the Docker image tag, then **AuthzForce - Installation and Administration Guide**) you can: | ||
|
|
||
| * **Create a domain** | ||
|
|
||
| ``` | ||
| curl -s --request POST \ | ||
| --header "Accept: application/xml" \ | ||
| --header "Content-Type: application/xml;charset=UTF-8" \ | ||
| --data '<?xml version="1.0" encoding="UTF-8"?><taz:domainProperties xmlns:taz="http://authzforce.github.io/rest-api-model/xmlns/authz/5" />' \ | ||
| http://<authzforce-container-ip>:8080/authzforce-ce/domains | ||
| ``` | ||
|
|
||
| * **Retrieve the domain ID** | ||
|
|
||
| ``` | ||
| curl -s --request GET http://<authzforce-container-ip>:8080/authzforce-ce/domains | ||
| ``` | ||
|
|
||
| * **Domain removal** | ||
|
|
||
| ``` | ||
| curl --verbose --request DELETE \ | ||
| --header "Content-Type: application/xml;charset=UTF-8" \ | ||
| --header "Accept: application/xml" \ | ||
| http://<authzforce-container-ip>:8080/authzforce-ce/domains/<domain-id> | ||
| ``` | ||
|
|
||
| * **User and Role Management Setup && Domain Role Assignment** | ||
|
|
||
| These tasks are now delegated to the [Identity Manager - Keyrock](http://catalogue.fiware.org/enablers/identity-management-keyrock) enabler. Here you can find how to use the interface for that purpose: [How to manage AuthzForce in Fiware](https://www.fiware.org/devguides/handling-authorization-and-access-control-to-apis/how-to-manage-access-control-in-fiware/). | ||
|
|
||
| ## User feedback | ||
|
|
||
| ### Documentation | ||
|
|
||
| All the information regarding the Dockerfile is hosted publicly on [Github](https://github.com/authzforce/server/tree/master/src/docker). | ||
|
|
||
| ### Issues | ||
|
|
||
| If you find any issue with this image, feel free to report at [Github issue tracking system](https://github.com/authzforce/server/issues). |
Oops, something went wrong.