Forum Stats

  • 3,749,908 Users
  • 2,250,074 Discussions
  • 7,866,687 Comments

Discussions

4.1 POST_LOGIN question

Jozis
Jozis Member Posts: 90 Blue Ribbon
edited Dec 21, 2011 12:29PM in APEX Discussions
Hello friends,

In my applications i have created custom login page. The purpose was to show more meaningful error messages if the authentication failed, like "Account locked" or "Account expired" ...
On login page I call my own authentication function. Depeding or the result the appropriate message is shown. If the authentication is successful - I call APEX_CUSTOM_AUTH.POST_LOGIN which registers the session.

It all worked well unitl I upgraded to Apex 4.1. Now POST_LOGIN keeps throwing that "Invalid login credentials" message. It looks that functionality of POST_LOGIN has been changed in 4.1.

Is there another way how to display custom messages if login was unsuccessful?

Thank you
Janis
Tagged:
«1345

Answers

  • Arie Geller
    Arie Geller Member Posts: 4,174 Gold Trophy
    Hello Janis,

    >> It looks that functionality of POST_LOGIN has been changed in 4.1.

    As far as I can tell, there isn’t any documentation regarding such a change in behavior. As POST_LOGIN is a documented procedure, the development team is also committed to maintain backward compatibility. Therefore, I’m guessing that functionality change is not your problem.

    I would try to create a simple new application, under the 4.1 instance, that uses the same custom authentication as the upgraded application, and see if the problem repeats itself.

    Regards,
    Arie.

    -------------------------------------------------------
    ♦ Please remember to mark appropriate posts as correct/helpful. For the long run, it will benefit us all.

    ♦ Author of Oracle Application Express 3.2 – The Essentials and More
  • Jozis
    Jozis Member Posts: 90 Blue Ribbon
    Thank you Arie.
  • MortenBraten
    MortenBraten Member Posts: 302 Bronze Badge
    It all worked well unitl I upgraded to Apex 4.1. Now POST_LOGIN keeps throwing that "Invalid login credentials" message. It looks that functionality of POST_LOGIN has been changed in 4.1.
    I am seeing the same thing... I am developing on an Apex 4.0 instance, and deploying to an Apex 4.1 (runtime-only) instance.

    In Apex 4.0 I am able to call APEX_CUSTOM_AUTH.POST_LOGIN and pass anything (some value, or null, does not matter) as the password parameter, and the Authentication Function defined in the authentication scheme does not seem to be called. This is actually desired behavior for me, as I simply want to "auto-login" a specific user without knowing the actual password. (I do not call APEX_CUSTOM_AUTH.LOGIN at all.)

    When the same application is deployed to the Apex 4.1 instance, the "Invalid Login Credentials" message is thrown, whereas in Apex 4.0 it succeeds, as described above.

    Hopefully someone from the Apex dev team can tell us what has changed, and how to deal with it...

    - Morten

    http://ora-00001.blogspot.com
  • Andyindo
    Andyindo Member Posts: 159
    I think this is the same problem I'm having.
  • Jozis
    Jozis Member Posts: 90 Blue Ribbon
    Should it be reported as a bug?
  • Andyindo
    Andyindo Member Posts: 159
    Possibly. I cant get my program to work and there was no problem before the upgrade to 4.1
  • MortenBraten
    MortenBraten Member Posts: 302 Bronze Badge
    Hopefully someone from the Apex dev team can tell us what has changed, and how to deal with it...
    Bump.

    - Morten

    http://ora-00001.blogspot.com
  • Vite DBA
    Vite DBA Member Posts: 600 Silver Badge
    Hi,

    as Apex is a supported product, if you've got a support contract for a database license, you could log a service request and push through what looks like a bug there. This will get a better response than waiting for someone to pick up the issue from a voluntary forum.

    Andre
  • MortenBraten
    MortenBraten Member Posts: 302 Bronze Badge
    as Apex is a supported product, if you've got a support contract for a database license, you could log a service request and push through what looks like a bug there. This will get a better response than waiting for someone to pick up the issue from a voluntary forum.
    That's true, but as you probably also know, the Apex team frequently visit this forum and respond to posts, especially about bugs and potential bugs.

    And since we are at least three people having the same problem, it's more useful to have this discussion in an open forum so that anyone can find it (also via Google), instead of "hiding" the issue/solution behind the MOS login.

    - Morten

    http://ora-00001.blogspot.com
  • Patrick Wolf-Oracle
    Patrick Wolf-Oracle Consulting Member of Technical Staff Posts: 2,448 Employee
    Hi guys,

    I'm currently on my way home from a business trip. I will have a look at the issue when I'm in the office next week and respond as soon as I know more.

    Regards
    Patrick
This discussion has been closed.