Accéder au contenu principal

Articles

Affichage des articles du décembre, 2015

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 butt

Oracle Sites Cloud Service - Themes

The Oracle Sites Cloud service comes with two themes : Basic  Launch. The launch theme provided OOTB is not suitable for small mobile devices. Something must be added : the viewport metadata as below: name = "viewport" content = "width=device-width, initial-scale=1.0" > in the following templates files   Launch/layouts/*.html

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=eyJpbnN0YW5jZWlkIjoiQTI0NUNFNUNFNjA5MjE1REZBRTA2RTQyRjExOThBNThFNzc4RDc5NzFDMkIiLCJzaWduZGF0ZSI6IjE0NTAxMDg1MDU3Mz