Wednesday, February 20, 2019

Peer Code Review Presentation at RMOUG Training Days 2019

I just finished giving my first presentation at RMOUG Training Days 2019. So far it has been a great event. The venue is very nice and convenient. The presentations cover interesting topics and are presented by experts. The organization has been flawless. A big thank you to the RMOUG team.

During my presentation I mentioned that I would provide a link to the artifacts of my presentation on this here it is:

There are three files:

I'd love to hear any stories of organizations putting this into practice.

Finally, a plug for my session tomorrow: APEX, ORDS and IoT. I hope to see you there.

Tuesday, February 12, 2019

Oracle APEX Consolidated Help

I recently had the need to show "most" of the application help on a single page in my APEX application. In order to make the procedure generic and easy to use, I didn't want to create any additional database objects--just a procedure to output what I needed. I decided to create a separate APEX Navigation List to create the hierarchy of pages that I want to include in the consolidated help page. The easiest way was to copy my "Desktop Navigation Menu" and then modify it. Of course, I could have just used "Desktop Navigation Menu" if it met my needs. The result looks like this

Others may need to do the same thing so I'm providing the code here. I apologize that I don't have good code formatting on this blog. I'm providing it as a standalone procedure, but you should put it in a package.

Thursday, February 07, 2019

Oracle APEX Less Social Sign-On with MS Azure and Office 365

After my last blog post a natural question came up: what if I'm a little anti-social?

Specifically, what if I do NOT want to make my APEX application available to everyone on the planet that has (or is willing to get) a Microsoft Azure / Office 365 account? What if I only want people in my company, that uses Azure AD, to be able to log in?

There are several ways you can do this, and I recommend you employ at least two. No, recommend is too lenient, I insist you employ at least two :). The first is to change the way you call the Microsoft OAuth2 provider. Instead of using the values in my last blog post:

Authorization Endpoint URL:
Token Endpoint URL:

Use the following:

Authorization Endpoint URL:
Token Endpoint URL:

For Insum, this would be

Authorization Endpoint URL:
Token Endpoint URL:

The method above does NOT secure your application to just your domain. It just makes it harder for someone to use another domain. A savvy user can bypass that by just typing "common" in the url.

The REAL step to secure your application is to do one or both of the following:

  1. Create an Authentication Scheme sentry function that makes sure the username includes @yourdomain
  2. Create Authorization Scheme that makes sure the username includes @yourdomain and apply it to the application.

I am often logged into multiple Azure AD accounts at the same time. By adding yourCompanyDomain to the Endpoint URLs you have the added bonus that users do not need to select a login each time they go to your application. Microsoft will detect the correct one to use.