Giter VIP home page Giter VIP logo

connect's People

Contributors

aloneh avatar azjezz avatar bocharsky-bw avatar fabpot avatar gido avatar grahamcampbell avatar iamluc avatar igorw avatar inalgnu avatar javiereguiluz avatar jderusse avatar jjarrie avatar lucasaba avatar lyrixx avatar marcw avatar nicolas-grekas avatar pborreli avatar pgrimaud avatar romainneutron avatar ruian avatar tgalopin avatar tucksaun avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

connect's Issues

js plugin to pull badges

hi, can we have a js plugin to pull badges to our blogs of badges?

one could take SDK and do this through knpbundles.com but maybe it is better from the source

Adds rewarding date for badges

I can see the rewarding date of any badge in my badgesBag, and for all others users.

For example, it could be interesting to know that for "Symfony Certification" and "Years" badges.

Private property access error after migrating to 4.3.0

Hello,
After migrating to version 4.3.0:

 - Updating sensiolabs/connect (v4.2.3 => v4.3.0): Loading from cache

I get this error

Error: Cannot access private property SensioLabs\Connect\Security\Authentication\Token\ConnectToken::$apiUser

.../vendor/sensiolabs/connect/src/SensioLabs/Connect/Security/Authentication/Token/SerializationConnectTokenTrait.php:9
.../vendor/symfony/security/Core/Authentication/Token/AbstractToken.php:174
...

Auth error handling is not perfect

This follows #47

When something goes wrong in a client application, during the login workflow, the user end up with a default message:

Warning! Authentication request could not be processed due to a system problem..
SensioLabsInsight needs access to your SensioLabsConnect account. Please accept the application in your Connect Apps preferences.

But actually, the end user (I in this case) did not "refuse" the oauth application. there is an SQL error.
But there is nothing in the log, and no exception. So the monitoring stack did not see it. And so the end user can not login anymore to the application.

If I turn my application in dev env, I can see this kind of logs:

[2014-10-13 16:05:27] security.INFO: Authentication request failed: An exception occurred while executing 'SELECT ...... FROM account_user a0_ WHERE a0_.uuid = ?' with params ["90f28e69-9ce9-4a42-8b0e-e8c7fcc27713"]: SQLSTATE[42703]: Undefined column: 7 ERROR: column a0_.workflow_id does not exist LINE 1: ...n_id12, a0_.beta AS beta13, a0_.admin AS admin14, a0_.workfl... ^ [] {"uuid":"06af53b6-838c-4568-bb75-2c445ebf0677"}

ping @tucksaun

Not getting all information of the user

I need the user's picture but I'm getting nothing from Connect:

properties: array:23 [▼
    "username" => "saro0h"
    "uuid" => "…"
    "name" => "Sarah Khalil"
    "image" => null
    …

The scope of my app is SCOPE_PUBLIC, I should access it right?

Unable to retrieve auth token

I'm trying to use sensiolabs/connect to retrieve a user's badges.
I've beeing trying to avoid the use of Silex but I couldn't complete the operation.
Then I've been trying with Silex and following the documentation.

When it comes to the connect/callback route, I have the following error:

ClientException:
file_get_contents(https://connect.sensiolabs.com/oauth/access_token):
failed to open stream: operation failed

An here's what it says:

[...]
at Browser->submit('https://connect.sensiolabs.com/oauth/access_token', array('client_id' => '9e...ac', 'client_secret' => '002...36', 'code' => 'b8...4b', 'grant_type' => 'authorization_code', 'redirect_uri' =>'http://badges.local/connect/callback', 'response_type' => 'code', 'scope' => 'SCOPE_PUBLIC')) in /var/www/badges/vendor/sensiolabs/connect/src/SensioLabs/Connect/OAuthConsumer.php line 93
at OAuthConsumer->requestAccessToken('http://badges.local/connect/callback', 'b8...4b') in /var/www/badges/web/index.php line 42
[...]

Is it possible that the problem is in: https://connect.sensiolabs.com/oauth/access_token ?

Without Silex the problem was the same: a 500 error from https://connect.sensiolabs.com/oauth/access_token

oauth with github

no sure if this is the right place for the request.

It would be great if one could login to connect.sensiolabs.com with a github account, and without to register just another account for another portal..

The SensioLabs Connect connection should redirect to the current page

This issue is related to the connect website and its integration in other Symfony/SensioLabs website, but there is no public issue tracker for it AFAIK, so I'm opening it on the SDK repo.

It is very annoying that each time you connect with SensioLabsConnect, you get redirected to the homepage of the website instead of staying on the current page. The redirection should go to the page where we were before the connection.

  • connect
  • insight
  • live
  • symfony
  • sensiolabs
  • trainings
  • profiler

Issues with serialization / deserialization of the token (and injected-objects)

There are a few issues with serialization / deserialization.
When serializing the token, everything is stored in the session storage. When restoring the session, there are a few issues, especially with external classes (such as the logger, in the case you use a Monolog stream handler, which doesn't have any protection against deserialization).

This issue is pretty simple to test.

Inside any Symfony2 controller of an application using ConnectBundle (apart from the interactive login), the following code should fail, monolog complaining about not being able to open the resource in case you set it up with a stream handler.

$user = $this->get('security.context')->getToken()->getApiUser()->refresh();

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.