Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 21 05:42
    gemron starred Erudika/scoold
  • Jan 20 14:30

    albogdano on master

    added simple /api/ping endpoint (compare)

  • Jan 20 10:45
  • Jan 20 09:38

    albogdano on master

    minor fixes to Dockerfile landing page (compare)

  • Jan 17 18:52
    MohamedElashri starred Erudika/scoold
  • Jan 16 16:21

    albogdano on master

    updated Dockerfile (compare)

  • Jan 16 05:20
    ripanioan starred Erudika/scoold
  • Jan 16 00:03
    pharrup starred Erudika/scoold
  • Jan 14 07:58
    sanxincao starred Erudika/scoold
  • Jan 13 08:37
    albogdano labeled #216
  • Jan 13 08:37
    albogdano opened #216
  • Jan 13 05:32
  • Jan 12 11:45
    yukimunet closed #215
  • Jan 12 11:45
    yukimunet commented #215
  • Jan 12 08:59
    albogdano commented #215
  • Jan 12 04:08
    yukimunet opened #215
  • Jan 11 21:20
    Travis Erudika/scoold (1.41.1) passed (328)
  • Jan 11 20:31

    albogdano on 1.41.1

    (compare)

  • Jan 11 20:31
    Travis Erudika/scoold (master) canceled (326)
  • Jan 11 20:31

    albogdano on master

    Release v1.41.1. (compare)

Alex Bogdanovski
@albogdano
you need to specify para.security.oauth.authz_url, para.security.oauth.token_url and para.security.oauth.profile_url
make sure that these are inside Scoold's config file, and that you restart Scoold after you set them
blemke1971
@blemke1971
Those were all set.
Alex Bogdanovski
@albogdano
this is what that error is telling me
did you update the para.access_key to be app:scoold as well as the secret
blemke1971
@blemke1971

Yes the para.access_key and secret are updated as well.

OpenID minimal setup

para.ms_app_id = "MyAppID"
para.ms_secret = "MySecret"
para.oa2_app_id = ""MyAppID"
para.oa2_secret = ""MySecret"
para.security.oauth.authz_url = "https://login.microsoftonline.com/147a2b71-5ce9-4933-94c4-2054328de565/oauth2/v2.0/authorize"
para.security.oauth.token_url = "https://login.microsoftonline.com/147a2b71-5ce9-4933-94c4-2054328de565/oauth2/v2.0/token"
para.security.oauth.profile_url = "https://graph.microsoft.com/oidc/userinfo"
para.security.oauth.scope = "openid email profile"
para.ms_tenant_id = "147a2b71-5ce9-4933-94c4-2054328de565"

Alex Bogdanovski
@albogdano
para.oa2_app_id = ""MyAppID" <-- double quotes
you can comment out para.ms_* properties
with #para.ms*
that error means that Para cannot find the configuration values for OAuth inside your app:scooldobject. Either these are not sent to Para correctly on Scoold startup or something else happens
on startup Scoold will send a bunch of config settings to be stored inside your Para app's settings field
you may have to refresh your browser cache as well because it could be using app:para for the auth request
blemke1971
@blemke1971
the refresh and the clearing out of the ms properties still seems to result in the same eror...
Alex Bogdanovski
@albogdano
@blemke1971 check your app settings by running para-cli setup then type in your app:scoold keys and then run para-cli app-settings
you should see "security.oauth.token_url": "..."
blemke1971
@blemke1971

well that doesnt seem to have anything in it.

{}

Alex Bogdanovski
@albogdano
then Scoold is not connecting to Para correctly
perhaps it's starting before Para has been started
blemke1971
@blemke1971
So the logs show para started at a timestamp of 13:11:16 and the first scoold message lists at 13:11:18
Alex Bogdanovski
@albogdano
maybe Para needs a few seconds more to accept the PUT /v1/_settings request from Scoold
also check the output of the command para-cli ping
blemke1971
@blemke1971
So there may be a connection issue here that is getting hidden somehow. if I use localhost in the para-cli I connect just fine. However if I use the value from para.endpoint is seems to hang. I get "New JWT Generated" but then it never returns
Alex Bogdanovski
@albogdano
yes, perhaps para.endpoint is incorrect
you can have para.endpoint = "http://para:8080" or para.endpoint = "http://localhost:8080"
blemke1971
@blemke1971
Yeah I cant use localhost in the scoold config because they are on two different docker containers so technically they are on two different hosts.
Alex Bogdanovski
@albogdano
that's why I don't like the networking in Docker - it always makes things a bit more complicated
blemke1971
@blemke1971
Part of me wants to pull this out of docker and install local.
blemke1971
@blemke1971
Is there a way of getting scoold pro without the docker image?
Alex Bogdanovski
@albogdano
I send out a newsletter with links to the JAR files on each new release
send me your email in a private message
blemke1971
@blemke1971
@albogdano I just wanted to touch base with you. I have installed para and scoold locally then started them. I was able to log in successfully and everything is running. So clearly something is horked with the docker configuration I have.
Alex Bogdanovski
@albogdano
@blemke1971 great! I'm glad you managed to make it work
I would suggest you find the correct local para endpoint inside docker and also use para.security.redirect_uri = "https://scoold.server.com" to make login redirects work. Related to this is #199
Alex Bogdanovski
@albogdano
try para.endpoint = "http://para:8080" or para.endpoint = "http://localhost:8080" or para.endpoint = "http://LOCAL_IP:8080"
blemke1971
@blemke1971
I got it working fully in docker. I feel like a bit of an idiot. The endpoint I switched to the docker hard coded IP with port and it started fine and is running as expected. Thank you so much for your time and effort.
Alex Bogdanovski
@albogdano
@blemke1971 nice! you are welcome! :thumbsup:
Paul M
@strvmarv
@albogdano Random question. Does a "StackOverflow import" import into the current space or always the default space?
Alex Bogdanovski
@albogdano
@strvmarv Posts from SO go to the default space on import. Does SO have spaces?
Paul M
@strvmarv
@albogdano Thanks. SO has different sub-domains and sites that link back to a single SSO login, but I don't recall anything similar to Spaces in Scoold.
joshoohaah
@joshoohaah
Question to about User management. Is it possible to make multiple 'Spaces' where ALL users can be invited? And when you have "ALL" ..is that just adding them all at a point in time..or can it be set so they will be generally available like the "Default" space? (It would be nice to just have an 'all' setting for a space so you don't have to keep going to re-add users as new users are created/added)
Alex Bogdanovski
@albogdano
@joshoohaah Spaces currently work more like private groups rather than public groups. Admins can add literally all users to any space but it's a manual operation. You have a good point that you have to re-add users later and it's repetitive. I will add a checkbox or something in the Admin panel when creating a space, like "add all users to this space". This area needs some more work and I'll get around to it soon. Thanks for the suggestion!
Alex Bogdanovski
@albogdano
I forgot to mention that there's a configuration option for automatically adding users to spaces: para.auto_assign_spaces = "my-space-one,my-other-space"
joshoohaah
@joshoohaah
@albogdano , thanks for that clarification! Yes you seem to have lots of 'hidden' configuration options. I love the flexibility here! Is there a documentation that shows all the exhaustive options available?
Alex Bogdanovski
@albogdano
@joshoohaah I try to add each option to the README but I guess a full list of options would also help
rafik777
@rafik777

@albogdano I think I discovered bug in newest version of scoold/para.
I've noticed high cpu usage (100%) of para process.
I've used VisualVM and found that CPU spends all time in thread in River class and logback debug method.
When i set logger level for River.class on debug I saw smth like this:

para_1    | 2021-01-21 00:04:27 [DEBUG] Pulled 1 messages from queue.
para_1    | 2021-01-21 00:04:27 [DEBUG] Message from queue: 
para_1    | 2021-01-21 00:04:27 [DEBUG] Waiting 5s for messages...
para_1    | 2021-01-21 00:04:27 [DEBUG] Pulled 1 messages from queue.
para_1    | 2021-01-21 00:04:27 [DEBUG] Message from queue: 
para_1    | 2021-01-21 00:04:27 [DEBUG] Waiting 5s for messages...
para_1    | 2021-01-21 00:04:27 [DEBUG] Pulled 1 messages from queue.
para_1    | 2021-01-21 00:04:27 [DEBUG] Message from queue: 
para_1    | 2021-01-21 00:04:27 [DEBUG] Waiting 5s for messages...
para_1    | 2021-01-21 00:04:27 [DEBUG] Pulled 1 messages from queue.
para_1    | 2021-01-21 00:04:27 [DEBUG] Message from queue: 
para_1    | 2021-01-21 00:04:27 [DEBUG] Waiting 5s for messages...
para_1    | 2021-01-21 00:04:27 [DEBUG] Pulled 1 messages from queue.
para_1    | 2021-01-21 00:04:27 [DEBUG] Message from queue: 
para_1    | 2021-01-21 00:04:27 [DEBUG] Waiting 5s for messages...
para_1    | 2021-01-21 00:04:27 [DEBUG] Pulled 1 messages from queue.
para_1    | 2021-01-21 00:04:27 [DEBUG] Message from queue: 
para_1    | 2021-01-21 00:04:27 [DEBUG] Waiting 5s for messages...
para_1    | 2021-01-21 00:04:27 [DEBUG] Pulled 1 messages from queue.
para_1    | 2021-01-21 00:04:27 [DEBUG] Message from queue:

LocalQueue.pull always returns "" when queue is empty and msgs list is never empty and sleep in loop is never invoked.

Alex Bogdanovski
@albogdano
@rafik777 Thanks for the report! I will fix this today.
rafik777
@rafik777
@albogdano Great! Thanks!
Aryan Khandal
@aryankhandal0
@albogdano the para.security.redirect_uri is not getting picked up in the last 3 scoold versions.
Alex Bogdanovski
@albogdano
@aryankhandal0 check your browser cache, and also the values inside /scripts/globals.js
It could be that the file is cached and the value of the global JS variable ENDPOINT is not changing