CapableObjects forum



Security Exception when calling IdForObject (ExternalIdServiceImpl)

Posted By Peter Buchmann 2014-01-21 17:50:05
Add to Favorites0

Security Exception when calling IdForObject (ExternalIdServiceImpl)

Author Message
Peter Buchmann
 Posted 2014-01-21 17:50:05
Supreme Being

Supreme Being - (41 091 reputation)Supreme Being - (41 091 reputation)Supreme Being - (41 091 reputation)Supreme Being - (41 091 reputation)Supreme Being - (41 091 reputation)Supreme Being - (41 091 reputation)Supreme Being - (41 091 reputation)Supreme Being - (41 091 reputation)Supreme Being - (41 091 reputation)

Group: Forum Members
Last Active: 2014-03-11 15:27:28
Posts: 230, Visits: 2 803
I just tried to get the Id for a object which has no default ECO_ID but a custom key. I get following error message:

Attempt by security transparent method 'Eco.Services.Impl.ExternalIdServiceBase.GetSoapEnvelopeForId(Eco.DataRepresentation.DefaultId)' to access security critical method 'System.Runtime.Serialization.Formatters.Soap.SoapFormatter..ctor()' failed.

Assembly 'Eco.Interfaces, Version=6.0.0.6733, Culture=neutral, PublicKeyToken=46a833be9e90de8c' is marked with the AllowPartiallyTrustedCallersAttribute, and uses the level 2 security transparency model. Level 2 transparency causes all methods in AllowPartiallyTrustedCallers assemblies to become security transparent by default, which may be the cause of this exception.

I remember that this worked in earlier versions. Aren't I allowed to query these ids or is this a bug?
HansKarlsen
 Posted 2014-01-21 18:36:50
Supreme Being

Supreme Being - (102 786 reputation)Supreme Being - (102 786 reputation)Supreme Being - (102 786 reputation)Supreme Being - (102 786 reputation)Supreme Being - (102 786 reputation)Supreme Being - (102 786 reputation)Supreme Being - (102 786 reputation)Supreme Being - (102 786 reputation)Supreme Being - (102 786 reputation)

Group: Administrators
Last Active: 2016-05-11 20:56:01
Posts: 608, Visits: 3 230
These things keep changing I am afraid, are you in the VS2010, or VS2012 or VS2013 build?
Peter Buchmann
 Posted 2014-01-21 20:26:43
Supreme Being

Supreme Being - (41 091 reputation)Supreme Being - (41 091 reputation)Supreme Being - (41 091 reputation)Supreme Being - (41 091 reputation)Supreme Being - (41 091 reputation)Supreme Being - (41 091 reputation)Supreme Being - (41 091 reputation)Supreme Being - (41 091 reputation)Supreme Being - (41 091 reputation)

Group: Forum Members
Last Active: 2014-03-11 15:27:28
Posts: 230, Visits: 2 803
We are in VS2012.
HansKarlsen
 Posted 2014-01-23 13:31:35
Supreme Being

Supreme Being - (102 786 reputation)Supreme Being - (102 786 reputation)Supreme Being - (102 786 reputation)Supreme Being - (102 786 reputation)Supreme Being - (102 786 reputation)Supreme Being - (102 786 reputation)Supreme Being - (102 786 reputation)Supreme Being - (102 786 reputation)Supreme Being - (102 786 reputation)

Group: Administrators
Last Active: 2016-05-11 20:56:01
Posts: 608, Visits: 3 230
After Reading I now Believe that we should drop the AllowPartiallyTrustedCallersAttribute marking for all Eco assemblies alltogether...

In .net4 it does not fill the purpose it used to in .net2 - and it has really only tagged along...
HansKarlsen
 Posted 2014-01-28 17:55:47
Supreme Being

Supreme Being - (102 786 reputation)Supreme Being - (102 786 reputation)Supreme Being - (102 786 reputation)Supreme Being - (102 786 reputation)Supreme Being - (102 786 reputation)Supreme Being - (102 786 reputation)Supreme Being - (102 786 reputation)Supreme Being - (102 786 reputation)Supreme Being - (102 786 reputation)

Group: Administrators
Last Active: 2016-05-11 20:56:01
Posts: 608, Visits: 3 230
AllowPartiallyTrustedCaller has been removed from vs2012 builds and onwards

Similar Topics

Expand / Collapse

Reading This Topic

Expand / Collapse

Back To Top