Maestro Linden commented at 2020-04-03T22:57:11Z

Hi nik, thanks for the report. I can reproduce this issue when I do the following:

1. UserA: Add a land-scoped experience to the list of experiences allowed in an estate

2. UserA: rez a box in the test region, with the following script: ```Java
   default
   {

   touch_start(integer total_number)
   {
       llSay(0, "Requesting experience permissions on " + llDetectedName(0) + "...");
       llRequestExperiencePermissions(llDetectedKey(0), "Do it!");
   }
   
   experience_permissions(key agent)
   {
       llSay(0, "Got experience permissions on " + llKey2Name(agent));
   }
   
   experience_permissions_denied(key agent, integer reason )
   {
       llSay(0, "Denied experience permissions for " + (string)agent + " due to reason #" + (string) reason);
   }
   

   }

   - Set the script experience to the same experience from step (1)
   

3. UserA: Go to a region in another private estate, and set the estate to

   • Disallow public access
   • Have the "Key Experiences" list set to the experience from step (1)

4. UserB (who is not in the test experience): login

5. UserB: attempt to visit the estate from (3)

   • Observe that UserB cannot enter (no access)

6. UserB: touch the scripted box from (2), and accept the experienceoffer

7. UserB: observe that you can now visit the estate from (3), due to being in the key experience

8. UserB: logout, and login to last location

   Expected results:
   In (8), UserB should still be able to visit the restricted estate on login.

   Actual results:
   In (8), UserB gets redirected to a safe location, as access to last location is denied. UserB is able to teleport to the restricted estate immediately after, however.