Home/ Questions/Q 8963615
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-15T16:23:48+00:00

I am having an issue that I hope you can help with. Let’s say

  • 0

I am having an issue that I hope you can help with. Let’s say I work for a hypothetical company called “Blammo”, and we have a hypothetical product called “Log”. I am trying to set up a system where someone could log in to logfromblammo.com and order some of our products, and then when they are ready to purchase go to checkout.blammo.com to pay for their order. Eventually I want to allow for Blammo to launch a new hypothetical product with it’s own website: rockfromblammo.com, and have that site also able to share a session with checkout.blammo.com so that users can have a single shopping cart across both product websites.

Naturally the hypothetical scenario described above is not how my company actually works, but it is a fair example of what I need to do. We have an existing user database, and we have ways to authenticate any of our users on any of our sites, but the goal I have is to allow users to cross seamlessly from one site to another without having to re-authenticate. This would also allow for us to seamlessly transfer data such as a shopping cart to the checkout site.

I have (briefly) looked at solutions such as OpenID, but I need to be able to integrate whatever solution we have with our existing authentication method, which is not terribly robust. Is there any good way to do this through PHP alone?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    What you could do is create “cross-over” links between the sites to carry the session over.

    The simplest way is to pass the session id via the query string; e.g.

    http://whateverblammo.com/?sessid=XXYYZZ

    Before you start thinking that anyone can trap that information, think about how your cookies are transferred; assuming you’re not using SSL, there’s not much difference for someone who taps the network.

    That doesn’t mean it’s safe; for one, users could accidentally copy/paste the address bar and thus leaking out their session. To limit this exposure, you could immediately redirect to a page without the session id after receiving it.

    Note that using mcrypt() on the session id won’t help much, because it’s not the visibility of the value that’s the problem; session hijacking doesn’t care about the underlying value, only its reproducibility of the url.

    You have to make sure the id can be used only once; this can be done by creating a session variable that keeps track of the use count:

    $_SESSION['extids'] = array();

$ext = md5(uniqid(mt_rand(), true)); // just a semi random diddy
$_SESSION['extids'][$ext] = 1;

$link = 'http://othersite/?' . http_build_query('sessid' => session_id() . '-' . $ext);

    When received:

    list($sid, $ext) = explode('-', $_GET['sessid']);
session_id($sid);
session_start();
if (isset($_SESSION['extids'][$ext])) {
    // okay, make sure it can't be used again
    unset($_SESSION['extids'][$ext]);
}

    You need these links every time a boundary is crossed, because the session may have gotten regenerated since the last time.

    • 0