<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Once the user is authenticated and the session is created, the server
will not ask for credentials again.<br>
You can of course provide your own login box. You can then call the
CreateSession to test if the credentials are valid.<br>
You cannot change the identity of the current session.<br>
<br>
This means that you can create a new session with the new credentials. <br>
With this session, you can download the layerdefintion and
featuresource.<br>
You can then store it in the other session's temporary repository, and
insert it into the runtime map.<br>
<br>
This is not a simple solution, but it works. It requires some manual
coding.<br>
<pre class="moz-signature" cols="72">Regards, Kenneth, GEOGRAF A/S
</pre>
<br>
<br>
dorra2007 skrev:
<blockquote cite="mid:13642851.post@talk.nabble.com" type="cite">
<pre wrap="">All users acess the same map (and layout), but the difference between users
consists in the temporary layers loaded, according to his parameters stored
in a database.
So, I am wondering if there is a mapguide security API that manages users in
this way, or a security and login code ready for use.I'll be very grateful
if you provide me with this code.
My problem is that users are not prompted for a login and password, while
they have also access denied.
James Card wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Tue, 06 Nov 2007 03:38:30 -0800, dorra2007 <a class="moz-txt-link-rfc2396E" href="mailto:dorrdor@yahoo.fr"><dorrdor@yahoo.fr></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I wish to know how to assign a user account to a layer (or layer
definition), so that when he wish access this layer, he will be promted
for a user name and password.
</pre>
</blockquote>
<pre wrap="">The workaround we used for this was to assign security at the map level
rather than the layer level. We created a separate map for each security
group that included only the layers appropriate to that group. We also
created one layout for each of these maps, so it was easy for the security
and login code already in place on the webserver to just load the
appropriate layout after the user was authenticated.
Since we only had four secuirty groups this was a simple solution. If the
were many different combinations of layer permissions required it would be
too cumbersome to maintain a separate map and layout for each.
--
James Card
209-578-5580
_______________________________________________
mapguide-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mapguide-users@lists.osgeo.org">mapguide-users@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/mapguide-users">http://lists.osgeo.org/mailman/listinfo/mapguide-users</a>
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
</body>
</html>