Specify iOS Keychain Access Group for SecureStorage

[tedrog36]

For iOS, I need the ability to specify the keychain access group for SecureStorage so that the information stored there can be accessed by the main host app as well as app extensions. This is primary reason I am not using SecureStorage.

This could be implemented similar to Preferences/Xam.Settings where a shareName can be specified.

[jamesmontemagno]

This would be a good addition. I think that on Android we could pass this in and store it in specific preferences and pass it down. We can have a default which most people will use and then this as an optional parameter. Thanks for the feature request.

[tedrog36]

No problem. Let me know if you need anything for the implementation since I have already done this in my own KeyChain class.

[jamesmontemagno]

If you want to send down a PR that would be cool ;)

[sasivishnu]

If the issue is still open, can I give a try to add this enhancement?

How do we like to pass down the value of KeyChain Access Group value to be used in SecRecord? Should we add constructor that takes this value?

[tedrog36]

I haven't looked at the Keychain object in SecureStorage in a while but I can tell you that is how I handled it in my Keychain classs.

public Keychain(string serviceName, string accessGroup)
{
	_serviceName = serviceName;
	_accessGroup = accessGroup;
}

[Johan-dutoit]

I created a local implementation last night.

I didn't go with the accessGroup in the constructor approach, as I figured someone might want to change it/not use it between calls. i.e. something keychain items should be sharable and others shouldn't.

That being said, my knowledge is somewhat limited to how the keychain works, as I remember reading somewhere that it if you don't specify an accessGroup it picks the first one from the list (not sure how accurate this is).

[jamesmontemagno]

PRs are accepted :)

[Johan-dutoit]

@jamesmontemagno I was about to submit a PR, however it's for iOS only and would put the other platforms in an unsupported state. Any ideas on how that should be implemented?

Android we could pass this in and store it in specific preferences and pass it down

When you said we can pass it in and store it in a specific preference, do you mean prefixing the key with the accessGroup value?

[jamesmontemagno]

I think that they are just ignored on Android/UWP, we can just document it.

[kenny128]

I might be misunderstanding what this issue is about but wasn't this feature supported in Xamarin.Auth?

[Andrec-Dxs]

Is this issue still pending to be solved?

[GMCristiano]

any news @jamesmontemagno ?