Custom Authentication failed after upgrade to Oracle APEX 18.2Custom basic authentication fails in IIS7Custom AuthorizeAttribute with custom authenticationC# WCF Session-based service with custom username/password validation: Configuration problemsOracle APEX 4.2 - Custom Authentication not workingOracle Apex Custom Authentication Error - 'MY_AUTHENTICATION' IS NOT A PROCEDUREHow to access tabular form data in oracle apex 18.2Remove Freeze Button Oracle APEXHow to solve Apex / Ords Configuration of Static FilesOracle Apex Authentication scheme?blank page loaded after downloading Oracle Apex

How could it be that 80% of townspeople were farmers during the Edo period in Japan?

How to handle professionally if colleagues has referred his relative and asking to take easy while taking interview

Why didn't Daenerys' advisers suggest assassinating Cersei?

How can I fix the label locations on my tikzcd diagram?

Is it standard for US-based universities to consider the ethnicity of an applicant during PhD admissions?

What are the effects of eating many berries from the Goodberry spell per day?

Is there a method to separate iron from mercury?

How come Arya Stark didn't burn in Game of Thrones Season 8 Episode 5

How to deal with the extreme reverberation in big cathedrals when playing the pipe organs?

How to know the path of a particular software?

What would a Dragon have to exhale to cause rain?

Single word that parallels "Recent" when discussing the near future

Why do academics prefer Mac/Linux?

Was the dragon prowess intentionally downplayed in S08E04?

Why does the U.S military use mercenaries?

multiline equation inside a matrix that is a part of multiline equation

Would it be fair to use 1d30 (instead of rolling 2d20 and taking the higher die) for advantage rolls?

Do high-wing aircraft represent more difficult engineering challenges than low-wing aircraft?

Pedaling at different gear ratios on flat terrain: what's the point?

Roman Numerals Equation 2

Why are lawsuits between the President and Congress not automatically sent to the Supreme Court

Find the area of the rectangle

A person lacking money who shows off a lot

Why use a retrograde orbit?



Custom Authentication failed after upgrade to Oracle APEX 18.2


Custom basic authentication fails in IIS7Custom AuthorizeAttribute with custom authenticationC# WCF Session-based service with custom username/password validation: Configuration problemsOracle APEX 4.2 - Custom Authentication not workingOracle Apex Custom Authentication Error - 'MY_AUTHENTICATION' IS NOT A PROCEDUREHow to access tabular form data in oracle apex 18.2Remove Freeze Button Oracle APEXHow to solve Apex / Ords Configuration of Static FilesOracle Apex Authentication scheme?blank page loaded after downloading Oracle Apex






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








1















My environment is:
Windows 10
XE 18C
Apex 18.2
Ords 18.4



I upgraded from Apex 5.1 and my custom authentication no longer works. When I attempt to login to my application 104 on page 101, after I input the Username and Password and press Login I get the following error message:



start l_return = 1 After update.. Set-Cookie:ORA_WWV_APP_104=ORA_WWV-FByLiIYz0y3yltgzZGNtjgdA; HttpOnly X-Content-Type-Options:nosniff X-Xss-Protection:1; mode=block Location:f?p=104:1:12616933237063:::::



I'm not really sure that this message indicates.
If I switch the authentication scheme to Application Express Authentication, the user authenticates fine.
Inside my custom authentication scheme I have the following variables set:



Scheme Type = Custom
Authentication Function Name = PKG_USERS.APEX_AUTHENTICATE_USER
Enable Legacy Authentication Attributes = No
Session Not Valid / Go To: = Login Page
Switch In Session = Disabled
Post-Logout URL = Home Page
Session Sharing = Application (No Sharing)


I tested the package: PKG_USERS.APEX_AUTHENTICATE_USER with the following test code in SQLDeveloper:



declare
p_user varchar2(512);
p_password varchar2(512);
p_temp_boolean boolean;
begin
p_user := '(my username)';
p_password := '(my password)';
p_temp_boolean := PKG_USERS.APEX_AUTHENTICATE_USER(p_user, p_password);
dbms_output.put_line('The return is: ' || sys.diutil.bool_to_int(p_temp_boolean));
end;


When I supply a proper Username / Password combination, the procedure returns 1. When I supply a wrong password, the procedure returns 0.



What changed from Apex 5.1 to 18 to cause an error with this authentication scheme?










share|improve this question






















  • Sorry, I can't help. Though, just to mention: I've also upgraded from 5.1.4 to 18.2, use custom authentication, and everything works OK (as far as authentication is concerned).

    – Littlefoot
    Mar 23 at 17:45











  • Thanks for responding. Did you install Apex 18.2 in a container (XEPDB1)? I wonder if that has anything to do with it?

    – user3138025
    Mar 23 at 19:08











  • You're welcome. No idea, as our database is 11g Enterprise Edition.

    – Littlefoot
    Mar 23 at 19:10

















1















My environment is:
Windows 10
XE 18C
Apex 18.2
Ords 18.4



I upgraded from Apex 5.1 and my custom authentication no longer works. When I attempt to login to my application 104 on page 101, after I input the Username and Password and press Login I get the following error message:



start l_return = 1 After update.. Set-Cookie:ORA_WWV_APP_104=ORA_WWV-FByLiIYz0y3yltgzZGNtjgdA; HttpOnly X-Content-Type-Options:nosniff X-Xss-Protection:1; mode=block Location:f?p=104:1:12616933237063:::::



I'm not really sure that this message indicates.
If I switch the authentication scheme to Application Express Authentication, the user authenticates fine.
Inside my custom authentication scheme I have the following variables set:



Scheme Type = Custom
Authentication Function Name = PKG_USERS.APEX_AUTHENTICATE_USER
Enable Legacy Authentication Attributes = No
Session Not Valid / Go To: = Login Page
Switch In Session = Disabled
Post-Logout URL = Home Page
Session Sharing = Application (No Sharing)


I tested the package: PKG_USERS.APEX_AUTHENTICATE_USER with the following test code in SQLDeveloper:



declare
p_user varchar2(512);
p_password varchar2(512);
p_temp_boolean boolean;
begin
p_user := '(my username)';
p_password := '(my password)';
p_temp_boolean := PKG_USERS.APEX_AUTHENTICATE_USER(p_user, p_password);
dbms_output.put_line('The return is: ' || sys.diutil.bool_to_int(p_temp_boolean));
end;


When I supply a proper Username / Password combination, the procedure returns 1. When I supply a wrong password, the procedure returns 0.



What changed from Apex 5.1 to 18 to cause an error with this authentication scheme?










share|improve this question






















  • Sorry, I can't help. Though, just to mention: I've also upgraded from 5.1.4 to 18.2, use custom authentication, and everything works OK (as far as authentication is concerned).

    – Littlefoot
    Mar 23 at 17:45











  • Thanks for responding. Did you install Apex 18.2 in a container (XEPDB1)? I wonder if that has anything to do with it?

    – user3138025
    Mar 23 at 19:08











  • You're welcome. No idea, as our database is 11g Enterprise Edition.

    – Littlefoot
    Mar 23 at 19:10













1












1








1








My environment is:
Windows 10
XE 18C
Apex 18.2
Ords 18.4



I upgraded from Apex 5.1 and my custom authentication no longer works. When I attempt to login to my application 104 on page 101, after I input the Username and Password and press Login I get the following error message:



start l_return = 1 After update.. Set-Cookie:ORA_WWV_APP_104=ORA_WWV-FByLiIYz0y3yltgzZGNtjgdA; HttpOnly X-Content-Type-Options:nosniff X-Xss-Protection:1; mode=block Location:f?p=104:1:12616933237063:::::



I'm not really sure that this message indicates.
If I switch the authentication scheme to Application Express Authentication, the user authenticates fine.
Inside my custom authentication scheme I have the following variables set:



Scheme Type = Custom
Authentication Function Name = PKG_USERS.APEX_AUTHENTICATE_USER
Enable Legacy Authentication Attributes = No
Session Not Valid / Go To: = Login Page
Switch In Session = Disabled
Post-Logout URL = Home Page
Session Sharing = Application (No Sharing)


I tested the package: PKG_USERS.APEX_AUTHENTICATE_USER with the following test code in SQLDeveloper:



declare
p_user varchar2(512);
p_password varchar2(512);
p_temp_boolean boolean;
begin
p_user := '(my username)';
p_password := '(my password)';
p_temp_boolean := PKG_USERS.APEX_AUTHENTICATE_USER(p_user, p_password);
dbms_output.put_line('The return is: ' || sys.diutil.bool_to_int(p_temp_boolean));
end;


When I supply a proper Username / Password combination, the procedure returns 1. When I supply a wrong password, the procedure returns 0.



What changed from Apex 5.1 to 18 to cause an error with this authentication scheme?










share|improve this question














My environment is:
Windows 10
XE 18C
Apex 18.2
Ords 18.4



I upgraded from Apex 5.1 and my custom authentication no longer works. When I attempt to login to my application 104 on page 101, after I input the Username and Password and press Login I get the following error message:



start l_return = 1 After update.. Set-Cookie:ORA_WWV_APP_104=ORA_WWV-FByLiIYz0y3yltgzZGNtjgdA; HttpOnly X-Content-Type-Options:nosniff X-Xss-Protection:1; mode=block Location:f?p=104:1:12616933237063:::::



I'm not really sure that this message indicates.
If I switch the authentication scheme to Application Express Authentication, the user authenticates fine.
Inside my custom authentication scheme I have the following variables set:



Scheme Type = Custom
Authentication Function Name = PKG_USERS.APEX_AUTHENTICATE_USER
Enable Legacy Authentication Attributes = No
Session Not Valid / Go To: = Login Page
Switch In Session = Disabled
Post-Logout URL = Home Page
Session Sharing = Application (No Sharing)


I tested the package: PKG_USERS.APEX_AUTHENTICATE_USER with the following test code in SQLDeveloper:



declare
p_user varchar2(512);
p_password varchar2(512);
p_temp_boolean boolean;
begin
p_user := '(my username)';
p_password := '(my password)';
p_temp_boolean := PKG_USERS.APEX_AUTHENTICATE_USER(p_user, p_password);
dbms_output.put_line('The return is: ' || sys.diutil.bool_to_int(p_temp_boolean));
end;


When I supply a proper Username / Password combination, the procedure returns 1. When I supply a wrong password, the procedure returns 0.



What changed from Apex 5.1 to 18 to cause an error with this authentication scheme?







custom-authentication oracle-apex-18.2






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 23 at 16:35









user3138025user3138025

3421623




3421623












  • Sorry, I can't help. Though, just to mention: I've also upgraded from 5.1.4 to 18.2, use custom authentication, and everything works OK (as far as authentication is concerned).

    – Littlefoot
    Mar 23 at 17:45











  • Thanks for responding. Did you install Apex 18.2 in a container (XEPDB1)? I wonder if that has anything to do with it?

    – user3138025
    Mar 23 at 19:08











  • You're welcome. No idea, as our database is 11g Enterprise Edition.

    – Littlefoot
    Mar 23 at 19:10

















  • Sorry, I can't help. Though, just to mention: I've also upgraded from 5.1.4 to 18.2, use custom authentication, and everything works OK (as far as authentication is concerned).

    – Littlefoot
    Mar 23 at 17:45











  • Thanks for responding. Did you install Apex 18.2 in a container (XEPDB1)? I wonder if that has anything to do with it?

    – user3138025
    Mar 23 at 19:08











  • You're welcome. No idea, as our database is 11g Enterprise Edition.

    – Littlefoot
    Mar 23 at 19:10
















Sorry, I can't help. Though, just to mention: I've also upgraded from 5.1.4 to 18.2, use custom authentication, and everything works OK (as far as authentication is concerned).

– Littlefoot
Mar 23 at 17:45





Sorry, I can't help. Though, just to mention: I've also upgraded from 5.1.4 to 18.2, use custom authentication, and everything works OK (as far as authentication is concerned).

– Littlefoot
Mar 23 at 17:45













Thanks for responding. Did you install Apex 18.2 in a container (XEPDB1)? I wonder if that has anything to do with it?

– user3138025
Mar 23 at 19:08





Thanks for responding. Did you install Apex 18.2 in a container (XEPDB1)? I wonder if that has anything to do with it?

– user3138025
Mar 23 at 19:08













You're welcome. No idea, as our database is 11g Enterprise Edition.

– Littlefoot
Mar 23 at 19:10





You're welcome. No idea, as our database is 11g Enterprise Edition.

– Littlefoot
Mar 23 at 19:10












1 Answer
1






active

oldest

votes


















0














I found the problem. It had to do with the Login page. The application was probably created in Apex 3.x. I made a new throw-away application in Apex 18.2 and then copied the new style of Login page to the migrated application.



New APEX applications use page 9999 as a login page. There are a few new fields added to the new style of login page. Once page 9999 was copied from the "throw-away" application, I removed the page alias of "LOGIN" from page 101 and added it to page 9999. After that, I was able to login and logout using my existing custom authentication scheme with no problem.






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function ()
    StackExchange.using("externalEditor", function ()
    StackExchange.using("snippets", function ()
    StackExchange.snippets.init();
    );
    );
    , "code-snippets");

    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "1"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55315953%2fcustom-authentication-failed-after-upgrade-to-oracle-apex-18-2%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    I found the problem. It had to do with the Login page. The application was probably created in Apex 3.x. I made a new throw-away application in Apex 18.2 and then copied the new style of Login page to the migrated application.



    New APEX applications use page 9999 as a login page. There are a few new fields added to the new style of login page. Once page 9999 was copied from the "throw-away" application, I removed the page alias of "LOGIN" from page 101 and added it to page 9999. After that, I was able to login and logout using my existing custom authentication scheme with no problem.






    share|improve this answer



























      0














      I found the problem. It had to do with the Login page. The application was probably created in Apex 3.x. I made a new throw-away application in Apex 18.2 and then copied the new style of Login page to the migrated application.



      New APEX applications use page 9999 as a login page. There are a few new fields added to the new style of login page. Once page 9999 was copied from the "throw-away" application, I removed the page alias of "LOGIN" from page 101 and added it to page 9999. After that, I was able to login and logout using my existing custom authentication scheme with no problem.






      share|improve this answer

























        0












        0








        0







        I found the problem. It had to do with the Login page. The application was probably created in Apex 3.x. I made a new throw-away application in Apex 18.2 and then copied the new style of Login page to the migrated application.



        New APEX applications use page 9999 as a login page. There are a few new fields added to the new style of login page. Once page 9999 was copied from the "throw-away" application, I removed the page alias of "LOGIN" from page 101 and added it to page 9999. After that, I was able to login and logout using my existing custom authentication scheme with no problem.






        share|improve this answer













        I found the problem. It had to do with the Login page. The application was probably created in Apex 3.x. I made a new throw-away application in Apex 18.2 and then copied the new style of Login page to the migrated application.



        New APEX applications use page 9999 as a login page. There are a few new fields added to the new style of login page. Once page 9999 was copied from the "throw-away" application, I removed the page alias of "LOGIN" from page 101 and added it to page 9999. After that, I was able to login and logout using my existing custom authentication scheme with no problem.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Mar 26 at 14:25









        user3138025user3138025

        3421623




        3421623





























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55315953%2fcustom-authentication-failed-after-upgrade-to-oracle-apex-18-2%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Kamusi Yaliyomo Aina za kamusi | Muundo wa kamusi | Faida za kamusi | Dhima ya picha katika kamusi | Marejeo | Tazama pia | Viungo vya nje | UrambazajiKuhusu kamusiGo-SwahiliWiki-KamusiKamusi ya Kiswahili na Kiingerezakuihariri na kuongeza habari

            SQL error code 1064 with creating Laravel foreign keysForeign key constraints: When to use ON UPDATE and ON DELETEDropping column with foreign key Laravel error: General error: 1025 Error on renameLaravel SQL Can't create tableLaravel Migration foreign key errorLaravel php artisan migrate:refresh giving a syntax errorSQLSTATE[42S01]: Base table or view already exists or Base table or view already exists: 1050 Tableerror in migrating laravel file to xampp serverSyntax error or access violation: 1064:syntax to use near 'unsigned not null, modelName varchar(191) not null, title varchar(191) not nLaravel cannot create new table field in mysqlLaravel 5.7:Last migration creates table but is not registered in the migration table

            은진 송씨 목차 역사 본관 분파 인물 조선 왕실과의 인척 관계 집성촌 항렬자 인구 같이 보기 각주 둘러보기 메뉴은진 송씨세종실록 149권, 지리지 충청도 공주목 은진현