Disallow All Objects by Default?

View: New views
2 Messages — Rating Filter:   Alert me  

Disallow All Objects by Default?

by No Spam-7 :: Rate this Message:

Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message

Is there a way I can set up my web application to disallow all access to services or objects, except for those I specify?
 
For example, I have a large API with many assemblies that will be on the web site, and adding Fluorine to the mix seems to expose the possibility of public access to my entire API.
 
I don't think I can use the Fluorine authorization or authentication scheme for this task, since it would be too easy to spoof. Likewise, the web.config classMappings and services elements don't seem like they'd do the job.
 
I'm new to Fluorine and my work is primarily on the .Net side of things, so I'm hoping I'm just missing something obvious here. Fluorine works great, but I can't use it if there's the slightest possibility my API could be hacked.
 
Chad

_______________________________________________
fluorine mailing list
fluorine@...
http://fluorine.thesilentgroup.com/mailman/listinfo/fluorine_fluorine.thesilentgroup.com

Re: Disallow All Objects by Default?

by Support-179 :: Rate this Message:

Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message

Chad,
 
FluorineFx by default disables access to all classes that are not public and marked with the [RemotingService] attribute.
 
Zoli


From: fluorine-bounces@... [mailto:fluorine-bounces@...] On Behalf Of No Spam
Sent: Thursday, April 17, 2008 5:08 PM
To: fluorine@...
Subject: [Fluorine] Disallow All Objects by Default?

Is there a way I can set up my web application to disallow all access to services or objects, except for those I specify?
 
For example, I have a large API with many assemblies that will be on the web site, and adding Fluorine to the mix seems to expose the possibility of public access to my entire API.
 
I don't think I can use the Fluorine authorization or authentication scheme for this task, since it would be too easy to spoof. Likewise, the web.config classMappings and services elements don't seem like they'd do the job.
 
I'm new to Fluorine and my work is primarily on the .Net side of things, so I'm hoping I'm just missing something obvious here. Fluorine works great, but I can't use it if there's the slightest possibility my API could be hacked.
 
Chad

_______________________________________________
fluorine mailing list
fluorine@...
http://fluorine.thesilentgroup.com/mailman/listinfo/fluorine_fluorine.thesilentgroup.com