What are web actions? Web actions can be explained as OpenWhisk actions annotated to quickly enable you to build web based applications as defined in the official documentation. If we compare an Openwhisk action and a web action, an OpenWhisk action that is not a web action requires both authentication and must respond with a JSON object. In contrast a web action can be invoked even without authentication and is capable of also passing additional data such as HTTP header, Status codes and returning body content of different types. What can we retrieve inside a web action? When invoking web actions they are capable of receiving additional HTTP request details as they are designed to facilitate features of HTTP invocations. __ow_method : The HTTP method of the request. __ow_headers : The request headers. __ow_user: The namespace identifying the OpenWhisk authenticated subject who created this web action. __ow_path:The attributes which are passed as path parameters into the ac
User provisioning and attribute profile mapping with Moodle and WSO2 Identity Server This is the continuation of how to configure SAML2 Web SSO with WSO2 Identity Server and Moodle. I will guide you on how the attribute mappings and user provisioning can be done using WSO2 Identity Server and Moodle. In order to do this we need to make sure that the attributes on the WSO2 Identity Server maps with the corresponding attributes in Moodle. This plugin provides the capability to auto provision users in Moodle. If a new user who is not registered in Moodle but is registered in the WSO2 Identity Server needs to be created in Moodle we can make use of these mappings. Let's get started on the configurations. First let's carry out the configs on the moodle end. 1) Same way as we did in the post [1]. Navigate to the Moodle's authentication plugins section and select the Settings of the OneLogin SAML SSO Authentication plugin. 2) Check the following two options.