Please upgrade here. These earlier versions are no longer being updated and have security issues.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Options

$100 - Helper Class for External Authentication Integration

13»

Comments

  • Options
    LincLinc Detroit Admin

    @jaredNZ said:
    And sorry but jsConnect is just lazy and bad practise.

    Shows what you know.

    @jaredNZ said:
    1 - It requires action from the user to sign up when they already are a member on your site

    You can make it seamless.

    @jaredNZ said:
    2 - Requires JS pings back and forth to server to do the auth using data on client side... insane?!

    It's built to allow the applications to reside on different servers, as is often the case.

  • Options
    jaredNZjaredNZ New
    edited June 2013

    You can make it seamless.

    By pinging back and forth with a several second delay. I did it, again, bad practise.

  • Options
    businessdadbusinessdad Stealth contributor MVP

    @jaredNZ said:
    By pinging back and forth with a several second delay. I did it, again, bad practise.

    I would say that, in this case, there is no absolute definition of "bad practice". JsConnect works in a scenario where the main website and the forum reside on different servers and/or under different second level domains, while your solution doesn't. Also, JsConnect decouples the main website from Vanilla implementation, whose core classes may change in a future version, while your solution is tightly coupled to a specific version. I would say that it's bad practice to interact directly with the core of a 3rd party application without using a proper API interface.

    Your approach might be better for your specific requirements, but I would not call it "absolutely better".

  • Options
    jaredNZjaredNZ New
    edited June 2013

    jsConnect being bad practise has nothing to do with my work around for there being no good way to integrate logins.

    Relying on the client having JS, and waiting several seconds to authenticate the forums is simply a bad user experience, does not deprecate tidily, and lazy because a true multi-server solution should work out these details server side in 50ms. Saying it needs to be multiserver is no excuse. Setup a CURL between servers and auth server-side, i.e. ProxyConnect

    But if Vanilla-Official wants to deprecate ProxyConnect and stick with jsConnect theres not much I can do other than work around it, and design my app with the best user experience in mind.

  • Options

    Given that you didn't successfully implement ProxyConnect, I think it is bit rich lecturing others.

    I think people have been polite enough to you, considering you know it all. You aren't really worth arguing with.

    grep is your friend.

  • Options

    Yup feel the same way, incredible staff would argue to keep the glaring holes in jsConnect.

    And like I've said 5x above - I did get ProxyConnect working. But it was unreliable; get some traffic (thousands) and X% of them don't have cookies enabled, or don't have X,Y,Z and bam - ProxyConnect fails under load.

    The bridge-script I posted above, that I offered to pay for, was apparently infinitely difficult for any of you to implement. It was 50 lines of PHP, like I said it would be. Perhaps you should listen to me if a newb without any experience in Vanilla can do what is so "infinitely hard" for all of you?

    Goodluck Vanilla.

  • Options

    @JaredNZ the best way you can help is figure out why your implementation isn't working. That way our Vanilla guys can try and make a solution for it.

    as soon as you have figured it out, document it on the Vanilla wiki please, that's what a community should be all about

    There was an error rendering this rich post.

  • Options
    businessdadbusinessdad Stealth contributor MVP
    edited June 2013

    Removed, not really important.

This discussion has been closed.