version 1.1.2.2, 2013/10/23 19:20:10
|
version 1.1.2.7, 2013/11/19 18:30:59
|
|
|
Pegasus webadmin interface provides a limited edition of administering the | Pegasus webadmin interface provides a limited edition of administering the |
cimserver through web. Currently, modification of cimserver config options | cimserver through web. Currently, modification of cimserver config options |
viewing the Providers registered and subscriptions view are supported. In | viewing the Providers registered and subscriptions view are supported. In |
future management of subscriptions and provider management will be added. |
future, management of subscriptions and provider management will be added. |
|
In OpenPegasus 2.14, Webadmin is still in a experimental vesrion and will |
|
be improved in the future. |
| |
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 |
Building source files for webadmin will need to build for both CIM-RS and |
is enabled by default. |
webadmin. CIM-RS is built as an integral part of server(not controlled by |
|
by build macros) and webadmin i controlled by PEGASUS_ENABLE_PROTOCOL_WEB, |
|
which is 'true by default'. |
|
To disable it set PEGASUS_ENABLE_PROTOCOL_WEB=false. |
|
|
|
What is relation between Webadmin and CIM-RS? |
|
============================================= |
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/yields payloads represented as JSON[2]. The |
in JSON can be consumed webserver and can be shown as a webpage. |
response in JSON can be consumed by webserver easily, for example through |
CIM-RS is built as a integral part of cimserver, not controlled by any env and |
javascripti, for displaying as a webpage. |
webserver facility is controlled by PEGASUS_ENABLE_PROTOCOL_WEB, which is |
|
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? |
=============================== | =============================== |
|
|
browser. For example, if your hostname is localhost.localdomain. Just type in | browser. For example, if your hostname is localhost.localdomain. Just type in |
localhost.localdomain:5988. | localhost.localdomain:5988. |
| |
Where do I put my custom webpages? |
Which ports do CIM-RS aand webadmin use? |
where does my webRoot points to? |
================== |
What are the security concern for using webadmin? |
Webadmin and CIM-RS currently uses the DMTF's CIMOM ports i.e 5988(http) and |
|
5989(https). This port will be updated with dedicated port for CIM-RS when |
|
available. |
|
|
|
Is there any security concerns for webadmin? |
|
================================================= |
|
In order to avoid modifying the server config options by any users, pegasus |
|
should be started with 'enableAuthentication=true' which forces users to login |
|
for the webadmin. |
|
and in order to restrict to particular groups, 'authorizedUserGroups' should be |
|
set to the groups, whose members should be allowed to modify the config |
|
options. |
|
EnableAuthentication and authorizedUserGroups details can be found in manpage |
|
of cimconfig(8) |
| |
| |
References: | References: |