3 Replies Latest reply: Mar 6, 2014 7:52 AM by VC RSS

    Identify a user in a mobile app

    cc13

      Hello,

       

      I created a mobile app with one page and a report region. Do I have an "easy" way to identify the user that is connected with my app without login-process? The report should show some figures for the current user, but this are no secret data.

       

      I know, with a login-process I have the username. But the reason for the mobile app is, that the user can access this with a shortcut on the mobile phone and do not have to put in the login credentials.

       

      Thanks,

      Carsten

        • 1. Re: Identify a user in a mobile app
          VC

          Create a public page and on first attempt to access that means if F_APP_USER is null prompt for username, store that value into a cookie

           

          After that you can derive the value from cookie and set into the F_APP_USER

           

          In case user clears the cookie- the page will prompt for username

          • 2. Re: Identify a user in a mobile app
            cc13

            Hi,

             

            I started a small app to test this.

             

            On the first page I have a text-item and a button. After the button is pressed the value of the text-item should be saved in the cookie. Here are the process for that:

             

            begin

               owa_util.mime_header('text/html', FALSE);

               owa_cookie.send(

                  name=>'CC13_COOKIE',

                  value=> :P1_USERNAME,

                  expires => sysdate + 365);

             

            exception

               when others then

                  null;

            end;

             

            But if I look in the chrome developer console I can not see this cookie. Whats wrong?

            • 3. Re: Identify a user in a mobile app
              VC

              Are you sure if the process is triggered?? what is the process point?

               

              Set it to before header and make sure the session state of the page item remains once the page is submitted.