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



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

Sessions, iFrames and maybe more

  • Filter
  • Time
  • Show
Clear All
new posts

  • Sessions, iFrames and maybe more

    I have a URL I need to post to get the user logged into an API.

    The problem is that the "standard" method of doing for this API is to actually redirect the user to the API's pages. I don't want to do that -- I want to log into the API, and have the user stay right on my page.

    I've tried what I can think of, and there's probably more than one way. One way would be:

    Call the URL as part of a page in an iframe. The problem with this is that the page in the iFrame isn't aware of the session variables of the logged-in user, which I need. Is there a way to make the session variables available to the page in the iframe?

    Another way is to use http_post(), and call that programatically. That works because I can pass in the user information from the session, and it does succeed with the login. But, it does not (and I don't want it to) redirect the current client browser, so the browser never gets the cookie from the API service, and the login is useless without the cookie. Tech support at the service tells me the login is good, but also says the browser needs to be aware that it has "visited" the site.

    So, any suggestions?

  • #2
    Re: Sessions, iFrames and maybe more

    Try this - your IFrame has as URL that points to their page. Just include your variables in the URL as parameters exactly as you did for your http_post operation. Your browser will have "visited" that other page.
    Steve Wood
    There is no Cloud. It's just someone else's computer.
    Web - Mobile - Hosting - Products - Frameworks - Developer Resources
    AlphaToGo | IADN (100% Alpha Anywhere Websites)


    • #3
      Re: Sessions, iFrames and maybe more

      Can't figure out how to do this Steve.

      Currently, I'm sending:

      FYI, the current URL ends with an encrypted JSON Web Token parameter:

      https://...?jwt=" + sParameter
      So, before the post, I've now tried:

      sString = "&session.username=" + session.username + "&session.userid=" + session.userID
      sUrl = sURL + sString
      The session.Username and session.userID are also the logins for the API, though of course the API makes no use of them here. And, it may even be failing at the API end - I don't know without bugging tech support again.

      Did you have something in mind other than this?


      • #4
        Re: Sessions, iFrames and maybe more

        I had to test because I did not know how session vars would behave in an IFrame. So if I run an IFrame from the parent like this:

        <iframe src=""></iframe>

        And then sampletest.a5w has this:

        <%A5 = id

        The CHILD knows's value provided in the IFrame URL. But the parent knows nothing of it.

        You cannot pass in the URL, it will create a variable named "" not a session variable.

        All the API's I have used send something back, and what they send back is enough to do whatever it is supposed to do. That would be using http_post or http_fetch(). From what I read, if you try to redirect the IFrame back to the parent (e.g., "visit" the API page, then redirect back to your page, using Javascript, again from what I read), you will cause a "cross-browser scripting error".
        Steve Wood
        There is no Cloud. It's just someone else's computer.
        Web - Mobile - Hosting - Products - Frameworks - Developer Resources
        AlphaToGo | IADN (100% Alpha Anywhere Websites)


        • #5
          Re: Sessions, iFrames and maybe more

          Thanks Steve. Yeah, I've asked this (well known) provider of the API if they might allow me to pass around some identifier, but I'm amazed to find out they hadn't thought of that. There's gotta be some way to do this...