Lack of information on how to use this library

[Repulser]

Im trying to use this library and am failing to understand how to use the token store, any insight would be much appreciated.

[caelcs]

Well no much to do... just need two things... annotate your Main Spring Boot application class and then make sure that you have the properties required.

You can have a look to this integration test to see how it works.

https://github.com/caelwinner/spring-security-mongo/blob/master/src/test/java/uk/co/caeldev/springsecuritymongo/MongoClientDetailsServiceIntegrationTest.java

[caelcs]

and one more thing, this library provides you all the beans that you may need to configure your different repositories like store, client credentials etc.
If you want to know how to configure the Spring OAuth2 using this library you can look at the project in my oath2-server and have a look to the spring oauth2 doc.

[Repulser]

By looking at the Oauth 2 server code, it seems that MongoTokenStore should be a bean?
Though Ive added the @EnableMongoSecurity annotation and still get
Parameter 1 of constructor in catalogue.mobile.AuthorizationServerConfig required a bean of type 'uk.co.caeldev.springsecuritymongo.MongoTokenStore' that could not be found.

[caelcs]

Hello have you added the properties ? Because that could be the only reason why the bean is not in the application context

…

Sent from my iPhone

On 4 Jan 2018, at 07:13, Repulser ***@***.***> wrote: By looking at the Oauth 2 server code, it seems that MongoTokenStore should be a bean? Though Ive added the @EnableMongoSecurity annotation and still get Parameter 1 of constructor in catalogue.mobile.AuthorizationServerConfig required a bean of type 'uk.co.caeldev.springsecuritymongo.MongoTokenStore' that could not be found. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[Repulser]

That was it!! thanks a lot, I added them and everything started working, one last question: is there a way to use my own mongo client and authenticate on my own?

[caelcs]

I dont know what you mean by that but so far this library is like an extension for Spring Security to use mongo instead of JDBC. there is no spring logic regarding to authentication.

…

On 4 January 2018 at 07:27, Repulser ***@***.***> wrote: That was it!! thanks a lot, I added them and everything started working, one last question: is there a way to use my own mongo client and authenticate on my own? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAxg7VCYpaj9nQgEL2WmBKVsbEKAnEtvks5tHH1YgaJpZM4RSBZ4> .

[caelcs]

you can always override the mongo client provided by defining your own and using the @primary annotation 👍

[Repulser]

I meant authenticating with mongo, the @Primary worked perfectly, thanks! though theres still the need to define the properties, is there a way to avoid this or should i just pseudo-define them?

[caelcs]

unfortunately it is mandatory for this version just because without those properties the default implementation wont work...

…

On 4 January 2018 at 11:23, Repulser ***@***.***> wrote: I meant authenticating with mongo, the @primary worked perfectly, thanks! though theres still the need to define the properties, is there a way to avoid this or should i just pseudo-define them? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAxg7e7u_gMZdhnpGN-tCd6ibrd4KUDBks5tHLSwgaJpZM4RSBZ4> .

[caelcs]

for the next version I could add the validation at the mongo client level and see how that works.

…

On 4 January 2018 at 11:35, Cael ***@***.***> wrote: unfortunately it is mandatory for this version just because without those properties the default implementation wont work... On 4 January 2018 at 11:23, Repulser ***@***.***> wrote: > I meant authenticating with mongo, the @primary worked perfectly, > thanks! though theres still the need to define the properties, is there a > way to avoid this or should i just pseudo-define them? > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#6 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AAxg7e7u_gMZdhnpGN-tCd6ibrd4KUDBks5tHLSwgaJpZM4RSBZ4> > . >

[caelcs]

What kind of feature are you trying to implement that the default Mongo client does not support?

…

On 4 January 2018 at 11:39, Cael ***@***.***> wrote: for the next version I could add the validation at the mongo client level and see how that works. On 4 January 2018 at 11:35, Cael ***@***.***> wrote: > unfortunately it is mandatory for this version just because without those > properties the default implementation wont work... > > On 4 January 2018 at 11:23, Repulser ***@***.***> wrote: > >> I meant authenticating with mongo, the @primary worked perfectly, >> thanks! though theres still the need to define the properties, is there a >> way to avoid this or should i just pseudo-define them? >> >> — >> You are receiving this because you commented. >> Reply to this email directly, view it on GitHub >> <#6 (comment)>, >> or mute the thread >> <https://github.com/notifications/unsubscribe-auth/AAxg7e7u_gMZdhnpGN-tCd6ibrd4KUDBks5tHLSwgaJpZM4RSBZ4> >> . >> > >

[Repulser]

Nothing really, im just using mongo for other things and would like to share the client, aswell as using different methods of authentication....
Removing the requirement for the properties would be nice, though ill just fill them with randomness for now.

[caelcs]

I have release version 2.0.0 adding only the Mongo Client when the properties has been set. Can I close this issue?