4 Replies Latest reply: Dec 11, 2012 9:28 AM by Ralf M. RSS

    authentication schema invalid after migration to 4.2

    Ralf M.
      I am testing an system migration.

      After the migration to Apex 4.2 our LDAP - authentication schema dont work.
      When I edit and save the schema - it works again - whats wrong?
      We have > 80 apps - I dont want to edit all individually. What can I do?

      additional info:
      hardware renewal (DL380 G5 -> DL370 G6 ; linux x64),
      migration single instance by Expdp fulldb (11.1/Apex 4.0) / impdp fulldb(11.2/Apex removed in target db before import) ,
      Upgrade Apex to 4.2

      regards Ralf
        • 1. Re: authentication schema invalid after migration to 4.2
          Christian Neumueller
          Hi Ralf,

          that's bug #14798940. It's on the Known Issues list and will be fixed in the upcoming 4.2.1 patchset. If you can not wait for the patchset, you can use the query below in SQL Commands, to get links to all the affected authentication schemes in your workspace:
          begin
            for i in ( select workspace,
                              application_id,
                              application_name,
                              scheme_type_code,
                              authentication_scheme_name,
                              authentication_scheme_id
                         from apex_application_auth
                        where is_current_authentication='Y'
                          and scheme_type_code = 'NATIVE_LDAP'
                          and attribute_05 is null
                        order by 1,2 )
            loop
              htp.p(apex_escape.html(i.workspace)||
                    ': '||
                    i.application_id||
                    ' '||
                    apex_escape.html(i.application_name)||
                    ': '||
                    '<a href='||'"f?p=4000:4495:&SESSION.::NO:RP,4495:FB_FLOW_ID,P4495_ID:'||
                    i.application_id||','||i.authentication_scheme_id||
                    '">'||
                    apex_escape.html(i.authentication_scheme_name)||
                    '</a><br/>');
            end loop;
          end;
          It should be a bit easier to change the authentication schemes by clicking through this list.

          Regards,
          Christian
          • 2. Re: authentication schema invalid after migration to 4.2
            Ralf M.
            Hi Cristian,

            thank you for the info.

            The query works well - I will use it to create a checklist ;-) ...

            thanx
            Ralf

            PS: I looked in the bug database and for the bug number #14798940? I dont found any info on "my oracle support". Whats the Subject of the Bug Message?
            • 3. Re: authentication schema invalid after migration to 4.2
              rorwessels
              Not sure if this will help much, but I had some issues with APEX and LDAP post upgrade to 4.2... I was directed to this... APEX_LDAP.is_member No Longer Works In APEX 4.2 (Doc ID 1507390.1)

              This links to a patch that addresses this issue and fixed my problem with those functions.
              • 4. Re: authentication schema invalid after migration to 4.2
                Ralf M.
                Thank you - but we are using own procedures/functions (using DBMS_LDAP) since 1.6 :-) ...

                regards Ralf