Thanks guys for your input. I made the changes you suggested and also made Geode sample's Github repo public: https://github.com/gtantachuco-pivotal/geode-security-samples What would the next steps be?
On Sat, Jul 11, 2015 at 12:07 PM, Jags Ramnarayanan <jramnara...@pivotal.io> wrote: > Guillermo, > Glad to see you are still active with Gem. Good article. > Few points on a quick glance: > > - You mention - "Cache server authentication allows a new server to join a > cluster. The locator is responsible for authenticating credentials of said > server. The first locator to join the cluster is assumed to be > authenticated and subsequent locators authenticate against the first one" > Strictly speaking it is responsibility of the membership coordinator to > authenticate subsequent ones. And, yes, when using locators, the first > locator will automatically be the coordinator. > > - Also important to point out that you should always run Gem cluster in a > secure domain making it super difficult to spoof the node executing the > coordinator. > > -- Jags > > > > > On Fri, Jul 10, 2015 at 6:02 PM, gtantachuco . <gtantach...@gmail.com> > wrote: > > > Dev team, > > I would like to publish this Geode security article to > > https://blogs.apache.org/geode/. Here is the initial draft. > > At your convenience, please can you let me know what the next steps would > > be to get this published? > > > > Thank you. > > > > -- > > Best regards, > > -Guillermo > > > > > -- Best regards, -Guillermo
