Element created through API ignores security

[Eric Johannsen]

I have a package in my EA repository that has a Group Lock for a group that I'm NOT a member of.

If I try to create a new requirement in that package using EA, I correctly get the message "The current action cannot be completed as the necessary security is not available".

HOWEVER, if I create a new requirement in that package, using the exact same user, through the API, the requirement is created and it does not inherit the group lock from the package it's in.

I'm using EA 6.5 Build 805 because this code needs to run for a number of different customers and 6.5 is the least common denominator.

Is this known behavior?  Is there a published work-around?