[mapguide-internals] Please review RFC 103

[Zac Spitzer]

taking a step back for a second,

how does this relate to the upcoming changes in

RFC 98 - EPSG/SRID Code Upgrade
https://trac.osgeo.org/mapguide/wiki/MapGuideRfc98

>From the motivation section of RFC 103 "For example, user can define
an EPSG code
mapping to a WKT if this EPSG code is not supported by MapGuide's
coordinate system. "



z

On 14 July 2010 12:34, Jason Birch <jason at jasonbirch.com> wrote:
> I would suggest that this kind of request should require author access AND
> should not be available through the API at all when authoring is disabled in
> webconfig.ini.  setDocument should require Administrator privileges.
>
> I am not a big fan of allowing public access to configuration documents,
> regardless of the seemingly innocuous nature of the information they
> contain.
>
> I guess the Fusion widget info calls access files outside of the repository.
>  Are there any others?
>
> Jason
>
> On 13 July 2010 16:24, Tom Fukushima wrote:
>
>> Along with SetDocument, what kind of user would be allowed access to this
>> file? For example, since the RFC mentions the Studio user perhaps these
>> operations only be available to someone with Author (or above) privileges.
>>  Do we need a way to set security on this document so that we can restrict
>> who can access it? I would hope not since that seems like overkill.
>>
>> Are there any other operations in MGOS that are similar to this (i.e.,
>> access documents or information outside of the repository) in behavior?
>>
>>
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>



-- 
Zac Spitzer
Solution Architect / Director
Ennoble Consultancy Australia
http://www.ennoble.com.au
http://zacster.blogspot.com
+61 405 847 168