Feature request : Security serialization/revert about unicorn

[kamsar]

Agreed, and I've thrown the idea around during previous release cycles. I haven't implemented it so far simply because the whole sync code and serialization formats are different; other than the idea of 'syncing' pretty much none of the item code carries over to security items.

I'll throw it in the ever growing hopper of things I wish Unicorn did. Feel free to implement if you have time before I do :)

[amitthakur2014]

Hi Kamsar,

Just wanted to know , the new functionality got implemented in new version of Unicorn

[kamsar]

Nope. It's not there yet.
On Thu, Nov 5, 2015 at 2:19 AM amitthakur2014 [email protected]
wrote:

Hi Kamsar,

Just wanted to know , the new functionality got implemented in new version
of Unicorn

—
Reply to this email directly or view it on GitHub
#30 (comment).

[cassidydotdk]

I don't think serialisation of security related information belongs in Unicorn, just my 2 cents. Changes to users/roles happen so infrequently in a project life cycle, managing process around this is not really a prime candidate choice for automation.

[el-slowmo]

I disagree. It is serializeable sitecore content that your code can depend
on.

For instance if you want to add user registration/authentication on your
site by using Sitecore users in a specific domain. You will want to
serialize that domain and add it to your source control, so you can deploy
the code and the sitecore items including the domain that go with your code.

On Fri, Dec 11, 2015, 10:11 AM Mark Cassidy [email protected]
wrote:

I don't think serialisation of security related information belongs in
Unicorn, just my 2 cents. Changes to users/roles happen so infrequently in
a project life cycle, managing process around this is not really a prime
candidate choice for automation.

—
Reply to this email directly or view it on GitHub
#30 (comment).

[kamsar]

Serialization of users, absolutely not.
Serialization of roles, I think makes sense.
Suppose you have a very multi site solution where each site has its own
roles, or devs are defining workflows and need to push dependent security
roles for the steps and transitions.

It is a totally separate concern from regular unicorn though as roles are
just a string and not an item. That's why this has sat on the shelf for so
long. New infrastructure for everything.
On Fri, Dec 11, 2015 at 1:35 AM el-slowmo [email protected] wrote:

I disagree. It is serializeable sitecore content that your code can depend
on.

For instance if you want to add user registration/authentication on your
site by using Sitecore users in a specific domain. You will want to
serialize that domain and add it to your source control, so you can deploy
the code and the sitecore items including the domain that go with your
code.

On Fri, Dec 11, 2015, 10:11 AM Mark Cassidy [email protected]
wrote:

I don't think serialisation of security related information belongs in
Unicorn, just my 2 cents. Changes to users/roles happen so infrequently
in
a project life cycle, managing process around this is not really a prime
candidate choice for automation.

—
Reply to this email directly or view it on GitHub
#30 (comment).

—
Reply to this email directly or view it on GitHub
#30 (comment).

[Eldblom-zz]

My opinion is that we should be able to serialise and version control everything if you wish to do so. This includes roles and users.
Naturally it's not sound to version control production users (or content for that matter) but for e.g. regression test purposes it is vital that you can store and version control complete environment configurations.

[kamsar]

There's no way to serialize users' passwords (or even the hashes thereof without direct SQL calls) which makes serializing users a bit pointless imo, as any deserialized user would only really be usable by a UserSwitcher or something as the password would not be moved.

[Eldblom-zz]

Good point. A file based membership provider could be the way to go for the automated test scenario.

On 12 Dec 2015, at 8:29 AM, Kam Figy [email protected] wrote:

There's no way to serialize users' passwords (or even the hashes thereof without direct SQL calls) which makes serializing users a bit pointless imo, as any deserialized user would only really be usable by a UserSwitcher or something as the password would not be moved.

—
Reply to this email directly or view it on GitHub.

[cassidydotdk]

While there may be a case for security information serialisation, I still don't see this as the job of Unicorn. It deals with Sitecore content in Sitecore databases. Membership data is neither content, nor does it sit in Sitecore databases.

A new tool, possibly as @eldblom suggests; file based membership, profile, and role providers - sure. Would be reasonably easy to implement as well. Or grab an existing one:

https://github.com/wilby/XmlMembershipProvider

[kamsar]

Moving this conversation to #107