Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Build 8301 Context.Security.CallResult Fails

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Build 8301 Context.Security.CallResult Fails

    I am seeing Context.Security.CallResult fail in 8301. I have been using the same code for years and never had this problem.

    Here is a simple function to test:

    Code:
    function testContextSecutityResult as c (e as p)
    
    if .not. Context.Security.CallResult.Success then
    error_generate(Context.Security.CallResult.Text)
    end if
    
    dim _loggedOnUser as c = Context.Security.CurrentUser
    
    dim js as c = "alert('" + js_escape(_loggedOnUser) + "');"
    
    testContextSecutityResult = js
    
    end function


    I am looking for someone to test this. Just add this function to a component that is using web security and execute it on a button.

    When I run it I get this:

    Untitled.png


    #2
    That's a worry - I just refused to move beyond 8099 - for this reason. Breaking live sites is not worth the progress in development of things I don't need.
    Insanity: doing the same thing over and over again and expecting different results.
    Albert Einstein, (attributed)
    US (German-born) physicist (1879 - 1955)

    Comment


      #3
      You're not using this code correctly. You're not doing anything before the if .not. Context.Security.CallResult.Success then line. That's why it is failing. I see no problem with context.security.

      Try this instead...

      Code:
      function testSecurity as c (e as p)
      
          dim doesUserExisit as l = .f.
          dim resultText as c = ""
      
          doesUserExisit = Context.Security.UserExists("TYPE_VALID_USERNAME_HERE")
      
          if .not. Context.Security.CallResult.Success then
              ' Something went wrong
              resultText = Context.Security.CallResult.Text
          else
              resultText = Context.Security.CallResult.Text
              testSecurity = "alert('" + js_escape(resultText) + "');"​
          end if
      
      end function​
      Last edited by mikeallenbrown; 08-29-2022, 11:42 AM.
      Mike Brown - Contact Me
      Programmatic Technologies, LLC
      Programmatic-Technologies.com
      Independent Developer & Consultant​​

      Comment


        #4
        Yes the code is complete.

        https://documentation.alphasoftware....rity/index.xml

        You must run it in a component that uses web security, and the user has logged in successfully.

        In build 7902 it returns the login of the current user.

        In build 8301 it fails.

        Try it and see what results you get.

        Comment


          #5
          See my updated post. I edited my response.
          Mike Brown - Contact Me
          Programmatic Technologies, LLC
          Programmatic-Technologies.com
          Independent Developer & Consultant​​

          Comment


            #6
            I changed your code so it returns a result if the CallResult succeeds or fails:

            Code:
            function testSecurity as c (e as p)
            
                 dim doesUserExisit as l = .f.
                 dim resultText as c = ""
            
                 doesUserExisit = Context.Security.UserExists("TYPE_VALID_USERNAME_HERE")
            
                 if .not. Context.Security.CallResult.Success then
                      ' Something went wrong
                      resultText = Context.Security.CallResult.Text
                      ' I added this line:
                      testSecurity = "alert('" + js_escape(resultText) + "');"
                 else
                      resultText = Context.Security.CallResult.Text
                      testSecurity = "alert('" + js_escape(resultText) + "');"
                 end if
            
            end function
            In 7902 it returns:
            Success.png

            In 8301 it returns:
            Untitled.png

            Comment


              #7
              When I run your code I get "Success".

              Mike Brown - Contact Me
              Programmatic Technologies, LLC
              Programmatic-Technologies.com
              Independent Developer & Consultant​​

              Comment


                #8
                Are you running it in build 8301?

                Comment


                  #9
                  Yes.
                  Mike Brown - Contact Me
                  Programmatic Technologies, LLC
                  Programmatic-Technologies.com
                  Independent Developer & Consultant​​

                  Comment


                    #10
                    Here is a short video demo: https://drive.google.com/file/d/14kv...ew?usp=sharing

                    You may need to wait a few minutes until Google is done with their processing. I just now uploaded it.
                    Mike Brown - Contact Me
                    Programmatic Technologies, LLC
                    Programmatic-Technologies.com
                    Independent Developer & Consultant​​

                    Comment


                      #11
                      Hmm...

                      It works for me when I run it exactly as you do in the video. Live Preview and localhost both work.

                      But when I run it in a UX inside a tabbed UI, it fails, and returns the "Unexpected exception" message.

                      So there is something else going on.

                      Comment


                        #12
                        You're not using this code correctly. You're not doing anything before the if .not. Context.Security.CallResult.Success then line.
                        OK I think I get it now. You are correct. A call must be made first, and then check if the ​call was successful.

                        I modified the code that first caused the error:

                        Code:
                        function testContextSecutityResult as c (e as p)
                        
                        dim _loggedOnUser as c = Context.Security.CurrentUser
                        
                        if .not. Context.Security.CallResult.Success then
                        error_generate(Context.Security.CallResult.Text)
                        end if
                        
                        dim js as c = "alert('" + js_escape(_loggedOnUser) + "');"
                        
                        testContextSecutityResult = js
                        
                        end function
                        What I don't understand is why it did not cause an error in build 7902. ​It should have.

                        As a result I stubbornly kept thinking this might be a bug in 8301. It is not.

                        Thank you.

                        Comment


                          #13
                          It is correct that Context.Security.CallResult should be used after a call to a property or method on Context.Security. However, Context.Security.CallResult should be benign if it is used first. i.e. Context.Security.CallResult.Success should return .T. if it is the first Context.Security property called in a request. That is a regression from 7902 to 8301. That regression will be fixed in the next build. The "correct" fix is moving the reference to Context.Security.CallResult.Success after the call to the Context.Security property or method.

                          Comment


                            #14
                            Sorry my bad on that - I've done everyone of these for my Hybrid Security Build - I should have spotted the inverted code.
                            Insanity: doing the same thing over and over again and expecting different results.
                            Albert Einstein, (attributed)
                            US (German-born) physicist (1879 - 1955)

                            Comment


                              #15
                              Ok so it is a bug. But my code was bad. I have now searched my project using Search in all Web Project Files (very handy). I found over 100 instances where I am using Context.Security.CallResult, but only the one where I had the code backwards.
                              Not sure how I did that, but it shows you how one tiny piece of code can cause havoc.
                              Attached Files

                              Comment

                              Working...
                              X