Couverture de Oracle Academy Tech Chat

Oracle Academy Tech Chat

Oracle Academy Tech Chat

De : Oracle Corporation
Écouter gratuitement

Offres de saison | 0,99 € par mois pendant les 3 premiers mois

5,99 €/mois par la suite. Des conditions s’appliquent. Annulation mensuelle possible.
À propos de ce contenu audio
Oracle Academy, Oracle's global philanthropic education program brings you Oracle Academy Tech Chat where we discuss how Oracle Academy helps prepare the next generation's work force. In this podcast Tyra Crockett, Senior Manager Oracle Academy North America, interviews experts across the Oracle ecosystem about their experience and advice for educators and their students.Oracle Corporation 2023 Economie Réussite personnelle
Épisodes
  • Congratulations You Just Gave Everyone Admin Access
    Nov 18 2026
    The application looks polished, the buttons work, and the demo is going perfectly—until an ordinary user opens the administrator dashboard. This episode explores how small configuration decisions can give people permissions they were never meant to have. We unpack authentication, authorization, roles, and the controls that protect pages, actions, and data. Drawing on Oracle Academy APEX learning, the conversation also examines why applications built with AI assistance still need human review and testing across different user roles. -------------------------- Transcript: Congratulations You Just Gave Everyone Admin Access An Oracle Academy Tech Chat episode in the It Worked on My Page APEX series Cold Open Tyra Peirce as narrator: It is demo day. The projector is on. The faculty advisor has found the one chair that squeaks every time anyone breathes. Lorilyn Owens as developer: Welcome to our new student services portal. You can update your profile, submit a request, and see information relevant to your role. Tyra Peirce as colleague: Nice. Can I try it? Lorilyn Owens as developer: Absolutely. I have prepared a test account. Tyra Peirce as colleague: Huh. Lorilyn Owens as developer: That is not the sound I wanted. Tyra Peirce as colleague: I can edit the employee directory. Lorilyn Owens as developer: That is definitely not supposed to happen. Tyra Peirce as colleague: I can also change approval statuses. Lorilyn Owens as developer: Please do not click anything else. Tyra Peirce as colleague: Too late. I found the admin dashboard. Would you like me to promote myself? Lorilyn Owens as developer: I would like you to slowly back away from the mouse. Tyra Peirce: Congratulations. You just gave everyone admin access. Lorilyn Owens: The page looks polished. The buttons work. The report loads. Then a different user signs in, and your helpful little app becomes a permission-granting golden retriever. It means well. It has no boundaries. Tyra Peirce: Welcome to Oracle Academy Tech Chat and our special APEX series, It Worked on My Page. Today we are looking at the difference between an app that runs and an app that knows who should be allowed to do what. Lorilyn Owens: And notice what did not happen in that opening. Nobody guessed a password or broke into the application. The colleague used the account they were given, clicked an ordinary link, and received access the developer never meant to provide. The missing control created the problem. Lorilyn Owens: We will also talk about AI-assisted development, because an AI tool can help you create an impressive page quickly. It cannot guess your organization's security rules unless you define them, implement them, and test them. Tyra Peirce: So before anyone promotes themselves during your next demo, let us fix the access model. A Working Page Is Only the Beginning Lorilyn Owens: When students build an app, the first milestone is usually visible. The form submits. The chart appears. The search finds the correct record. Those are real accomplishments, and they are satisfying because you can point to them. Tyra Peirce: Security work is easier to overlook because success often looks like nothing happened. A student tried to open an administrator page and could not. A reviewer could see a request but could not rewrite the student's profile. The system quietly said no in exactly the right place. Lorilyn Owens: That quiet no is a control working correctly. If the app manages advising requests, club budgets, equipment loans, internship applications, or employee information, different users have different responsibilities. The interface should reflect those responsibilities, and the application must enforce them. Tyra Peirce: A control is simply a deliberate check that prevents an action the user should not be able to take. The user may be curious, confused, rushing, or clicking a link a teammate sent them. The control should still protect the page, action, or data without depending on perfect behavior. Tyra Peirce: This is where the phrase It worked on my page becomes dangerous. The developer tested while signed in with a powerful account. Everything worked because that account could do everything. That test proved the feature could run. It did not prove the access design was correct. Lorilyn Owens: A better question is: what happens when the requester, reviewer, approver, and administrator each sign in? If the answer is exactly the same for all four, your app may have skipped an important design meeting. Authentication and Authorization Tyra Peirce: Let us separate two words that are often mixed together. Authentication answers, Who are you? It establishes the user's identity through the application's sign-in method. Lorilyn Owens: Authorization answers, Now that the application knows who you are, what are you permitted to see and do? Can you open this page? View this report? Edit this record? Approve this request? Manage other users? Tyra Peirce: Think about a concert...
    Afficher plus Afficher moins
    21 min
  • Why Is My Report Showing 12,000 Rows?
    Nov 18 2026

    The user asked for today's thirty-two registrations. The report returned twelve thousand. This episode investigates how filters, session state, table relationships, and saved report settings can produce results far beyond what anyone expected. We explore why developers need to define what one row represents and verify which records belong in the result. Connecting Oracle Academy SQL and APEX learning, the conversation shows how a clear user question becomes an accurate, useful report—and why making an oversized report prettier rarely solves the underlying problem.

    --------------------

    Afficher plus Afficher moins
    13 min
  • The Button that did Absolutely Nothing
    Nov 18 2026

    You complete the form, click Save, and wait. The button changes color, but did anything actually happen? This episode follows an apparently broken button through the complete APEX workflow: page submission, validation, conditions, processing, data changes, and user feedback. Along the way, we explore how developers can investigate problems methodically and help users understand the result of their actions. The story brings Oracle Academy APEX concepts together around a practical lesson: a reliable application needs every step behind the click to work together.

    --------------

    Afficher plus Afficher moins
    13 min
adbl_web_anon_alc_button_suppression_t1
Aucun commentaire pour le moment