version 1.1.2.5, 2013/11/15 08:48:09
|
version 1.1.2.6, 2013/11/18 11:00:57
|
|
|
| |
How to build pegasus for using webadmin? | How to build pegasus for using webadmin? |
======================================== | ======================================== |
If you are building from sources, No need to set any build environ variable. It |
If you are building from sources, No need to set any build environ variable. |
is enabled by default. |
It is enabled by default. |
webadmin interface's backbone is CIM-RS details at [1] and webserver facility | webadmin interface's backbone is CIM-RS details at [1] and webserver facility |
built on pegasus. CIM-RS accepts payload represented as JSON[2]. The response | built on pegasus. CIM-RS accepts payload represented as JSON[2]. The response |
in JSON can be consumed webserver and can be shown as a webpage. | in JSON can be consumed webserver and can be shown as a webpage. |
CIM-RS is built as a integral part of cimserver, not controlled by any env and |
CIM-RS is built as a integral part of cimserver, not controlled by any env |
webserver facility is controlled by PEGASUS_ENABLE_PROTOCOL_WEB, which is |
and webserver facility is controlled by PEGASUS_ENABLE_PROTOCOL_WEB, which is |
enabled by default. To disable it set PEGASUS_ENABLE_PROTOCOL_WEB=false. | enabled by default. To disable it set PEGASUS_ENABLE_PROTOCOL_WEB=false. |
| |
How do I bring up the webadmin? | How do I bring up the webadmin? |
|
|
| |
What port is uses? | What port is uses? |
================== | ================== |
For this release(OpenPegasus 2.14), the port is fixed and not able to change. The port is 5988. |
Webadmin and CIM-RS currently uses the DMTF's CIMOM ports i.e 5988(http) and |
In the furture release , the port will be able assigned. |
5989(https). This port will be updated with dedicated port for CIM-RS when |
|
available. |
| |
where does my webRoot points to? | where does my webRoot points to? |
=============================== | =============================== |
|
|
| |
What are the security concern for using webadmin? | What are the security concern for using webadmin? |
================================================= | ================================================= |
|
The two usual scenarios about security authentication and authorizations |
The security is enabled by default in the release version.To disable it,set | The security is enabled by default in the release version.To disable it,set |
enableAuthentication=false when start cimserver. When PAM is enabled, webadmin is | enableAuthentication=false when start cimserver. When PAM is enabled, webadmin is |
able to access by the system users, otherwise the cim users needs to be added by | able to access by the system users, otherwise the cim users needs to be added by |
the tool cimuser.Authorization is still not clear until a role based authorization is |
the tool cimuser.Authorization is still not clear until a role based authorization |
implemented in the future release. |
is implemented in the future release. |
| |
| |
What is relation between Webadmin and CIM-RS? | What is relation between Webadmin and CIM-RS? |
================================================================= | ================================================================= |
Webadmin is based on the restful services which is defined by DMTF DSP0210. |
Webadmin is based on the CIM-Restful services(CIM-RS) which is defined by [1]. |
http://dmtf.org/sites/default/files/standards/documents/DSP0210_1.0.0.pdf |
As of pegasus 2.14, CIM-RS support is partial and this support will be done |
From OpenPegasus 2.14, CIM-RS will be supported partly. |
phase by phase. |
| |
| |
References: | References: |