[Feature Request] Option to continue to leverage a separate, discrete XCreds Shares profile (like NoMAD)

[dstranathan]

Request to have the option of store all XCReds Shares data in its own dedicated profile (like NoMAD).

Having the XCreds Shares keys in the main XCreds profile is useful for those who want a single profile to manage, but may not be optimal for those of us who are managing a lot of business-critical SMB shares.

A couple reasons to consider offering a dedicated XCreds Shares profile:

1. I have over 50+ shares to manage. It's messy when these keys are stored in the main XCreds profile. I need ~7 keys per share = 350 lines of XML...that's a LOT of profile bloat!

2. The likelihood of updating the main XCreds profile in production will be rare, (only once or twice year I hope), but my org adds SMB shares several times a year as new departments are added (we bring on new research labs, and each lab gets a SMB share which needs to be in XCreds). This means I may have to touch the XCreds profile more than Id like to. I want to avoid the potential for 'collateral damage' if something gets messed up in a main XCreds profile update. If a stand-alone Shares profile gets corrupted, sure, that's bad, but at least users can still manually mount a share, but but if the main XCreds keys are in a bad state then ALL of the XCReds login/sync keys might be missing/broken. Yikes.

Something to consider?

I realize that Tim added all Shares keys into the main XCreds profile for simplicity, but in my org's case, having 2 discrete profiles is more efficient, safe, and managable.