Skip to content

Support for multiple accounts and service account authentication#18

Open
aschempp wants to merge 10 commits into
Happyr:masterfrom
aschempp:feature/clients
Open

Support for multiple accounts and service account authentication#18
aschempp wants to merge 10 commits into
Happyr:masterfrom
aschempp:feature/clients

Conversation

@aschempp

@aschempp aschempp commented Aug 4, 2016

Copy link
Copy Markdown
Collaborator

This PR adds two features:

  1. You can have multiple accounts / multiple google client IDs.
    Use e.g. happyr.google.api.default_analytics and happyr.google.api.special_youtube with different credentials.
  2. New support for "service account" credentials. Our application uses Google Analytics information in the backend, so we need server-to-server communication. See https://developers.google.com/identity/protocols/OAuth2ServiceAccount for information from Google.

Everything should be fully BC with existing version (automatically converting the bundle configuration). I have been using the service authentication with client v1 for over a year now, it works well. I just added client v2 now and will test that implementation soon.

Let me know what you think :-)

@aschempp

Copy link
Copy Markdown
Collaborator Author

As promised, v2 tested and works as expected 😎

@aschempp

aschempp commented Nov 8, 2016

Copy link
Copy Markdown
Collaborator Author

Any update on this PR ?

@srslynow

Copy link
Copy Markdown

Nice work, thanks @aschempp

@aschempp

Copy link
Copy Markdown
Collaborator Author

will this get merged somewhen?

@aschempp

aschempp commented Feb 4, 2019

Copy link
Copy Markdown
Collaborator Author

@Nyholm @cakper is there anything I can do to get this merged?

@cakper

cakper commented Feb 4, 2019

Copy link
Copy Markdown

@aschempp I'm not involved in this project anymore, @Nyholm would you be able to help?

@Nyholm Nyholm left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's quite a large change and no tests.

Im happy you are using this bundle. What do you say if we merge this and tag 3.0?

Could you rebase this and then write a entry in the changelog?

* {@inheritDoc}
*/
public function load(array $configs, ContainerBuilder $container)
public function loadInternal(array $config, ContainerBuilder $container)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why this change?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The ConfigurableExtension is just a shortcut with helper methods.

@aschempp

aschempp commented Feb 7, 2019

Copy link
Copy Markdown
Collaborator Author

Im happy you are using this bundle. What do you say if we merge this and tag 3.0?

The changes are supposed to be backwards compatible, so there's no need for v3 from my side. As you can see, it has been a while (Aug 2016) when I implemented this. I'm still actively using that fork, but I'd love to see this in the core.

What would you say if I create separate branches and pull requests for the separate features? I can also look at the unit tests in that case. Or would you say its too much work to review every detail and just get a 3.0 out?

@ddonnini

ddonnini commented Feb 8, 2019

Copy link
Copy Markdown
Contributor

Thanks, @aschempp, I missed your PR! I think there are too many changes as you pointed out, maybe open different PRs would be better for @Nyholm!

* Add symfony 4 compatibility

* Remove useless compatibility for symfony/yaml

(cherry picked from commit 9238275)
@aschempp

Copy link
Copy Markdown
Collaborator Author

Sorry for the delay. I will create separate PRs as soon as I can find some time. I'm still actively using that feature, so I won't forget about it.

@Nyholm

Nyholm commented Nov 23, 2019

Copy link
Copy Markdown
Member

#SymfonyHackday

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants