[mapguide-internals] Using MapGuide credentials for featuresources

[Haris Kurtagic]

Thanks Bruce, I will try to edit xml manually and check it.
It would be great if there would be standard way of defining this for
all FDO providers.

Haris

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org
[mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Bruce
Dechant
Sent: Thursday, November 01, 2007 10:48 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Using MapGuide credentials for
featuresources

Haris,

1) The "Use MapGuide Credentials" appears for specific FDO providers in
Studio. Studio has custom feature source editors for certain providers
that it is aware of, otherwise it uses a generic feature source editor.
Tom would know more about how and if it is even possible to extend this
to other 3rd party providers.

2) The code is all handled internally by the MapGuide server here
MgTagManager::SubstituteTags().
   You simply specify the credentials in the feature source document as
an example and MapGuide does the rest.

<FeatureSource xsi:noNamespaceSchemaLocation="FeatureSource-1.0.0.xsd">
  <Provider>Autodesk.Oracle</Provider>
  <Parameter>
    <Name>Username</Name>
    <Value>%MG_USERNAME%</Value>
  </Parameter>
  <Parameter>
    <Name>Password</Name>
    <Value>%MG_PASSWORD%</Value>
    </Parameter>
  <Parameter>
    <Name>Service</Name>
    <Value>ADSKTUX2</Value>
  </Parameter>
  <Parameter>
    <Name>DataStore</Name>
    <Value>ALLTYPES</Value>
  </Parameter>
  <ConfigurationDocument>config.xml</ConfigurationDocument>
</FeatureSource>

3) As far as I know FDO doesn't support a parameter scheme so clients
know what to do here. MapGuide doesn't pass the above parameters on to
FDO. It replaces the tags with the actual data before calling FDO.

Thanks,
Bruce

-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org
[mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Haris
Kurtagic
Sent: November 1, 2007 3:42 PM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Using MapGuide credentials for feature
sources

Hi Bruce,

I believe I will have some more question's on this but for now just few
of them ( this is topic I was very interested in several months ago) :)

1. I saw checkbox "Use MapGuide credentials" for Autodesk Oracle
provider but never been able to get it for King.Oracle provider.
   So my question is when this checkbox is displayed or what custom FDO
provider needs to do to get the checkbox displayed ?

2. It was several months ago , I was looking for any implementation of
that functionality in MG ( looking in code how MG creates FDO connection
) and I couldn't find the relation's to using MG user for FDO
connection. Please, can you point me to that specific part of the code ?

3. In FDO specs there is no ( or I can't find ) anything how to write
specific connection properties UserName/Password which will be later set
by FDO clients like MG ?

Haris


-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org
[mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Bruce
Dechant
Sent: Thursday, November 01, 2007 10:08 PM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] Using MapGuide credentials for feature
sources

Hi All,

This question came up in the PSC meeting that I unfortunately missed.

In Studio when you specify the "Use MapGuide credentials" for the
feature source there are 2 parameters that will get substituted in the
feature source when it is accessed they are %MG_LOGIN_USERNAME% and
%MG_LOGIN_PASSWORD%.
MapGuide will substitute the currently connected user login credentials
when this feature source is accessed. So ensure that when you use this
type of credentials that the underlying feature source has a matching
user/password for when you login.

A potential cause for error when using it this way is that when you are
authoring a map and creating a feature source this way you are an
"Administrator" and then later test it out in your web browser as an
"Anonymous" user. One user may have access to the feature source and the
other may not.

Thanks,
Bruce


_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals