Accéder au contenu principal

Oracle Sites Cloud Service - Adding authentication to a site

With Oracle Sites Cloud Services, access to any site is Public, by default. If you have to add authentication, there is a very simple way to achieve it:

First, we assume that authentication will be against the existing Identity Domain provided with the tenant.

In a dedicated page of a site, called Login for instance, we add an App component which embeds an URL to any folder of Documents Cloud Service.
ie:
App URL = 
https://documents.XX.oraclecloud.com/documents/embed/home/nameasc

 Note that the URL will be called with the EMBED keyword.
Then we add the App component is a region, and  we setup a height=1 and a width=1 (almost invisible).
That's all.
Each time a user will navigate to this custom  Login Page, and if the user is not yet authenticated, a new page will splash on the screen, asking for credentials. Once login and pasword are provided by the user, the page disapears and return to custom Login page.



Optionnaly it's possible to add a dedicated button which triggers a logout by adding this link:
https://myservices.us2.oraclecloud.com/mycloud/faces/adfAuthentication?
logout=true&end_url=https://documents.sites.us2.oraclecloud.com//

Prerequisites: Authorize Documents Cloud Service to embed Folder in an iframe and add the domain to the granted list. (In Administration menu)

Other advantages: If you have a subscription to Database Service in the same Identity Domain, the method described above will be a good way to introduce an authentication to an APEX component.
Cf my other post related to Apps.

Commentaires

Enregistrer un commentaire

Posts les plus consultés de ce blog

Oracle Documents Cloud Service - Using Upload File REST API

If the Upload File sample given in ODCS documentation is used "as is", we get a http 400 error. The syntax is strict and every blank line must be empty (no space character for instance). If we cust and paste the sample, there are residual space characters which must be removed. So, use this pattern instead: -----1234567890 Content-Disposition: form-data; name="jsonInputParameters" { "parentID": " " } -----1234567890 Content-Disposition: form-data; name="primaryFile"; filename="example.txt" Content-Type: text/plain Hello World! -----1234567890-- instead the original one: -----1234567890 Content-Disposition: form-data; name="jsonInputParameters" { "parentID":"FB4CD874EF94CD2CC1B60B72T0000000000100000001" } -----1234567890 Content-Disposition: form-data; name="primaryFile"; filename="example.txt" Content-Type: text/plain -----1234567890-- Tests can be...
3 commentaires
Lire la suite

Oracle Sites Cloud Service - Apps

It's possible to add kinds of widgets (named APPS) inside any page of a site built with Oracle Sites Cloud Service (SCS). Any app is materialized by two URL: a Renderer Url which will render any HTML fragment inside an iframe tag at runtime a settings url which will be rendrered at design time in the settings menu. all URLs must be called through https (meaning that the called server has to be ssl enabled) In the following samples, we integrate: a dummy app (a simple html page produced with node.js) which demonstrates the parameteres caried by the Sites Cloud engine when calling the backend server,  a regular Apex report or form,  a custom report which calls a rest api generated by Apex /ORDS Sample node.js server.js below is a sample of parameter values get from a dummy node.js server Main call id=26e45e21-dbb6-4877-9886-482b37213d2f instance=eyJpbnN0YW5jZWlkIjoiQTI0NUNFNUNFNjA5MjE1REZBRTA2RTQyRjExOThBNThFNzc4RDc5NzFDMkIiLCJzaWduZGF0ZSI6IjE0NTAxMDg1M...
Enregistrer un commentaire
Lire la suite

Configuring Oracle Cloud as the Service Provider with SimpleSAMLphp as IDP

In order to establish SSO between enteprise backend and Oracle Public Cloud, it's possible to use SimpleSAMLphp (Federation tool) as an in-house Identity Provider , and setup Oracle Cloud as the Service Povider . Cf official documentation Managing Single Sign-On about the concept. SSO relies on SAML 2.0 standard. Tasks At the Identity Server (IDP) level Install Apache and PHP 5.3 + Install SimpleSAMLphp Just Follow documentation and  yum install php53-mcrypt   instead php-mcrypt if linux complains about it. Test with a simple SP provided with SimplePHPphp. Don't forget to un-comment the  example-userpass ! Export the metadata in a XML file At the Cloud Service level Import the previous metadata file Accept default values and don't change anything. At the IDP server level:  Follow documentation Servive Provider Quickstart Update the config/authsources.php with infos provided in the parameter pages (entity Id) EntityID value must be the sam...
Enregistrer un commentaire
Lire la suite