Assume Control of API about seat

[leonjza]

I am assuming you are talking about CSV imports. The admin that imported the APIs via CSV own the keys. There is no way to know which SeAT user owns said key by a keyID. There has also never been a version that supports mass importing keys either (except via the SeAT API). If you mass imported keys, you have to transfer the ownership via the keys details to a SeAT user.

When you add an API key using the normal API Key Management, then the person that added the key also owns it.

[drkthunder02]

I just remember putting in api's by hand on the old version, and then when a user logged on with the same api key by putting it onto his profile, the user being able to assume control of the api. There was no transfer ability back on 0.x version of SeAT.

[leonjza]

Ah yes. We can add the automatic ownership change when adding a key.