|
version 1.1.2.6, 2013/11/18 11:00:57
|
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 | In OpenPegasus 2.14, Webadmin is still in a experimental vesrion and will |
| be improved in the future. | 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. |
Building source files for webadmin will need to build for both CIM-RS and |
| It 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 |
javascripti, for displaying as a webpage. |
| and 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. |
| | |
| What port is uses? |
Which ports do CIM-RS aand webadmin use? |
| ================== | ================== |
| Webadmin and CIM-RS currently uses the DMTF's CIMOM ports i.e 5988(http) and | 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 | 5989(https). This port will be updated with dedicated port for CIM-RS when |
| available. | available. |
| | |
| where does my webRoot points to? |
Is there any security concerns for webadmin? |
| =============================== |
|
| webRoot is the path that webadmin pages locate. Following are the value of |
|
| webRoot for part of the platforms. |
|
| |
|
| Linux /opt/tog-pegasus/www |
|
| i5/PASE /QOpenSys/QIBM/UserData/UME/Pegasus/www |
|
| Windows <PEGASUS_HOME>/www |
|
| zOS /var/wbem/www |
|
| |
|
| Where do I put my custom webpages? |
|
| =============================== |
|
| The custom webpages can be put in to webRoot and the types are limited to the |
|
| ones in mimeTypes.txt. |
|
| |
|
| What are the security concern for using webadmin? |
|
| ================================================= | ================================================= |
| The two usual scenarios about security authentication and authorizations |
In order to avoid modifying the server config options by any users, pegasus |
| The security is enabled by default in the release version. To disable it,set |
should be started with 'enableAuthentication=true' which forces users to login |
| enableAuthentication=false when start cimserver. When PAM is enabled, webadmin is |
for the webadmin. |
| able to access by the system users, otherwise the cim users needs to be added by |
and in order to restrict to particular groups, 'authorizedUserGroups' should be |
| the tool cimuser.Authorization is still not clear until a role based authorization |
set to the groups, whose members should be allowed to modify the config |
| is implemented in the future release. |
options. |
| |
EnableAuthentication and authorizedUserGroups details can be found in manpage |
| |
of cimconfig(8) |
| What is relation between Webadmin and CIM-RS? |
|
| ================================================================= |
|
| Webadmin is based on the CIM-Restful services(CIM-RS) which is defined by [1]. |
|
| As of pegasus 2.14, CIM-RS support is partial and this support will be done |
|
| phase by phase. |
|
| | |
| | |
| References: | References: |
Return to
readme.webadmin
CVS log
Up to [Pegasus] / pegasus