authzforce/serverThis image of a minimal AuthzForce Server runtime is intended to work together with Identity Manager - Keyrock and PEP Proxy Wilma generic enabler.
This image gives you a minimal installation for testing purposes. The AuthzForce Installation and Administration guide on readthedocs.org (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-11.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-11.0.0
As stands in the AuthzForce Installation and administration guide on readthedocs.org (select the version matching the Docker image tag, then AuthzForce - Installation and Administration Guide) you can:
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-container-ip>:8080/authzforce-ce/domains
curl -s --request GET http://<authzforce-container-ip>:8080/authzforce-ce/domains
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>
These tasks are now delegated to the Identity Manager - Keyrock enabler. Here you can find how to use the interface for that purpose: How to manage AuthzForce in Fiware.
All the information regarding the Dockerfile is hosted publicly on Github.
If you find any issue with this image, feel free to report at Github issue tracking system.
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
在 Linux 系统配置镜像服务
在 Docker Desktop 配置镜像
Docker Compose 项目配置
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
MacOS OrbStack 容器配置
在宝塔面板一键配置镜像
Synology 群晖 NAS 配置
飞牛 fnOS 系统配置镜像
极空间 NAS 系统配置服务
爱快 iKuai 路由系统配置
绿联 NAS 系统配置镜像
QNAP 威联通 NAS 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
无需登录使用专属域名
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
免费版仅支持 Docker Hub 访问,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。
专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等;免费版仅支持 docker.io。
当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。
通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。
先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。
使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
来自真实用户的反馈,见证轩辕镜像的优质服务