Want to create your own Oracle APEX "Open Door"? authentication scheme

Want to create your own Oracle APEX "Open Door" authentication scheme

Have you tried to use the Oracle APEX “Open Door Credentials” authentication scheme? You didn’t like the Login page but don’t know how to change it. This is exactly the situation I found myself in not too long ago so I have written this article to show you how to change the “Application Express Accounts” authentication scheme to behave like the “Open Door Credentials” scheme, and you can customize to your heart’s content. Follow the simple steps below and see for yourself.

Firstly, customize the Login page 101 by adding company logo, text or URL as desired assuming you have already created an APEX application.

Change P101_PASSWORD type from Password to Hidden because we just want to capture the username (P101_USERNAME) but don’t care about the password.

Go to the Processing section on page 101 and do not change the Set Username Cookie process.

At this point you will need to create a new APEX user account called APP109_USER (or any name you want) for authentication purpose so no individual APEX account is needed to run this application. It’s effectively the “Open Door Credentials” authentication concept.

If you don’t have the required privilege to create new APEX user account then ask your APEX administrator for assistance. Don’t forget to get the password.

Go back to page 101 Processing section and select the Login process. Modify the PL/SQL code to replace P101_USERNAME with the common user APP109_USER in the authentication package. Enter the appropriate password for APP109_USER and in this case it is ‘Year2017’.

Do not change the Clear Page(s) Cache process.

Ensure your application still uses the “Application Express Accounts” authentication scheme.

Here is the new look of the Login page and you can enter whatever you like in the Username field. Now you can share this application with anyone without needing an APEX user account.

If you want to reference the Username entered on the Login page then you will need to create an application level item called APP_USERNAME (or any name you like).

After creating the APP_USERNAME item go back to page 101 Processing section. Select the Login process and modify the PL/SQL to assign the value of P101_USERNAME to APP_USERNAME.

Run the application again and enter the desired user name to login.

I have modified the Home page to display APP_USER and APP_USERNAME so you can see the difference. APP_USER is the common user we use for APEX authentication so everyone will be logging in as APP109_USER in this example.

The LOGIN USER is the user name entered on the Login page and subsequently saved to the application item APP_USERNAME.

Here is the Home page displaying both authenticated user (APP_USER) and the login user name (APP_USERNAME). Both users are referenceable throughout the APEX application.

Hope you’d find this article useful.













Nikita Sindwani

Associate Lead Software Engineer at TSYS|Global Payments

7 年

What if we want to use googleid or facebookid for authentication.How will we implement this?

回复
Tony Kirn

Technology Product Owner - Enterprise Database

8 年

Thanks Tommy. Very useful information.

要查看或添加评论,请登录

Tommy Tang的更多文章

  • Azure Cosmos DB and High Availability

    Azure Cosmos DB and High Availability

    5 November 2019 I went to Microsoft Cosmos DB hands-on workshop a few weeks ago and came back with renewed enthusiasm…

  • Multi-Cloud Resilience Architecture Pattern

    Multi-Cloud Resilience Architecture Pattern

    4 August 2019 Recently I have heard comments made by a senior IT Executive questioning why can’t we have Active-Active…

    19 条评论
  • Are you ready for Multi-Cloud

    Are you ready for Multi-Cloud

    28 April 2019 Lately I have heard colleagues earnestly discussing (or perhaps debating) the prospect of adopting…

    15 条评论
  • Is Disaster Recovery Really Worth The Trouble (Part 4)

    Is Disaster Recovery Really Worth The Trouble (Part 4)

    11 March 2019 In this final chapter of the Disaster Recovery discussion I am going to explore some of the common…

  • Is Disaster Recovery Really Worth The Trouble (Part 3)

    Is Disaster Recovery Really Worth The Trouble (Part 3)

    24 February 2019 In previous articles I’ve emphasised Disaster Recovery (DR) design principle is simply about…

    1 条评论
  • Is Disaster Recovery Really Worth The Trouble (Part 2)

    Is Disaster Recovery Really Worth The Trouble (Part 2)

    11 February 2019 In the previous article I've mentioned Architecture is the foundation, the bedrock, for implementing…

    1 条评论
  • Is Disaster Recovery Really Worth The Trouble (Part 1)

    Is Disaster Recovery Really Worth The Trouble (Part 1)

    3 February 2019 Often when you talk to your IT colleagues or business owners about protecting their precious system…

  • Having Pizza Tonight

    Having Pizza Tonight

    A simple way to explain the different Cloud services I'm not sure if you have come across this pizza analogy used for…

    1 条评论
  • Oracle Unified Approach to Data Management

    Oracle Unified Approach to Data Management

    Most customers I have spoken to found it increasingly costly to manage large amount of corporate data but hesitant to…

  • Oracle IaaS and Open Source

    Oracle IaaS and Open Source

    You think Oracle Cloud is too expensive for software development? Well I have created a simple Book Recommendation…

社区洞察

其他会员也浏览了