It's a little frustrating to see that Github is holding SAML hostage with a more expensive business plan. SAML integrations should be par for the course with any SaaS solution.
Powerful new features for businesses on GitHub.com
51–60 of 60 posts
Re: Powerful new features for businesses on GitHub.com
#52Earlier quoted context omitted.
That's what people used to do before because there were no good options to provision separate work accounts for people. With the new for business model I'm guessing we'll see people being issued work accounts and keeping their personal GitHub accounts completely separate, which might be a good thing.
Developers have the same identity no matter who they work for. It makes sense to separate access ("this person has access to Example Corp's repos only as long as they work for Example Corp") from identity ("this person owns this account"). Introducing single-sign-on as one way to simplify login, and potentially as a second-factor for gaining access to repositories run by the business, makes sense. Making developers c…
But it's not just about having access to example corp. If I log in to GitHub from my work laptop then my company technically has access to my personal GitHub account and the repos of any other organization I happen to belong to. It goes the other way around to. If an attacker hacks my personal laptop and I'm logged into GitHub then they have access to all of my companies repositories.
There are perfectly valid reasons for segregating accounts so that there is complete separation between them.
Re: Powerful new features for businesses on GitHub.com
#53Earlier quoted context omitted.
Developers have the same identity no matter who they work for. It makes sense to separate access ("this person has access to Example Corp's repos only as long as they work for Example Corp") from identity ("this person owns this account"). Introducing single-sign-on as one way to simplify login, and potentially as a second-factor for gaining access to repositories run by the business, makes sense. Making developers c…
But it's not just about having access to example corp. If I log in to GitHub from my work laptop then my company technically has access to my personal GitHub account and the repos of any other organization I happen to belong to. It goes the other way around to. If an attacker hacks my personal laptop and I'm logged into GitHub then they have access to all of my companies repositories. There are perfectly valid reason…
That's why I'm saying it may make sense to separate identity from access.
Re: Powerful new features for businesses on GitHub.com
#54Earlier quoted context omitted.
I think we should give it a few months to see if the fact that it doesn't look good is inherent to the color or just because we've become accustomed to it looking one way for so long. I can't count the number of interface redesigns I've seen in services I used that I hated at first and now I look back at the old design and can't fathom how I ever thought it was better. And if colorblind people aren't inconvenienced (…
Fair enough. Side note: I'm surprised there isn't a specific header browsers could send for something like colorblindness. That would allow sites to react to that header and serve up a different stylesheet.
Isn't that what the accept header is for? Telling the server what content types you're willing to accept, including relevant parameters. Something like:
Accept: text/css; color-blind=trichromatic
Re: Powerful new features for businesses on GitHub.com
#55Earlier quoted context omitted.
That's what people used to do before because there were no good options to provision separate work accounts for people. With the new for business model I'm guessing we'll see people being issued work accounts and keeping their personal GitHub accounts completely separate, which might be a good thing.
Developers have the same identity no matter who they work for. It makes sense to separate access ("this person has access to Example Corp's repos only as long as they work for Example Corp") from identity ("this person owns this account"). Introducing single-sign-on as one way to simplify login, and potentially as a second-factor for gaining access to repositories run by the business, makes sense. Making developers c…
It is the first scenario not the second. The person is gaining access to the GitHub organization via SAML SSO. They are bringing their own identity and do not lose access.
Re: Powerful new features for businesses on GitHub.com
#56Earlier quoted context omitted.
Developers have the same identity no matter who they work for. It makes sense to separate access ("this person has access to Example Corp's repos only as long as they work for Example Corp") from identity ("this person owns this account"). Introducing single-sign-on as one way to simplify login, and potentially as a second-factor for gaining access to repositories run by the business, makes sense. Making developers c…
But it's not just about having access to example corp. If I log in to GitHub from my work laptop then my company technically has access to my personal GitHub account and the repos of any other organization I happen to belong to. It goes the other way around to. If an attacker hacks my personal laptop and I'm logged into GitHub then they have access to all of my companies repositories. There are perfectly valid reason…
You company only managed your membership in the GitHub organization. It doesn't have access your personal account or the details within it.
Re: Powerful new features for businesses on GitHub.com
#57It's a little frustrating to see that Github is holding SAML hostage with a more expensive business plan. SAML integrations should be par for the course with any SaaS solution.
It's because it's one of the few things an enterprise can't cheap out on. They have to have it.
Re: Powerful new features for businesses on GitHub.com
#58Earlier quoted context omitted.
This is for colourblind people.
Still doesn't make it look good. If thats an issue they could always have an optional setting to enable colorblind mode.
Why not have colorblind mode be the default? Much more courteous to make the nitpickers change their mode than casual browsers who just want to be able to use the site.
Re: Powerful new features for businesses on GitHub.com
#59Earlier quoted context omitted.
Fair enough. Side note: I'm surprised there isn't a specific header browsers could send for something like colorblindness. That would allow sites to react to that header and serve up a different stylesheet.
Isn't that what the accept header is for? Telling the server what content types you're willing to accept, including relevant parameters. Something like: Accept: text/css; color-blind=trichromatic Of course no server would recognize this today, since afaik the CSS media type doesn't define any parameters other than perhaps `charset`, but the mechanism is there at least. Also any self respecting web server would just i…
[deleted]
Re: Powerful new features for businesses on GitHub.com
#60Earlier quoted context omitted.
But it's not just about having access to example corp. If I log in to GitHub from my work laptop then my company technically has access to my personal GitHub account and the repos of any other organization I happen to belong to. It goes the other way around to. If an attacker hacks my personal laptop and I'm logged into GitHub then they have access to all of my companies repositories. There are perfectly valid reason…
You company only managed your membership in the GitHub organization. It doesn't have access your personal account or the details within it.
It does if I am logged in on a company laptop and they control access to that laptop. (This is hypothetical in this case, I happen to know that the particular company I work at does not have any backdoors on my laptop).