Bump shiro-spring from 1.4.0 to 1.7.1 in /17.Spring-Boot-Shiro-Session

[dependabot[bot]]

Bumps shiro-spring from 1.4.0 to 1.7.1.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

[AlexCline]

Are you working with two accounts on a single install? There are other issues reported when working with this setup.

[kevvan]

Ya, I guess I hadn't come across that issue yet.

[madmaze]

I second this, I have 4 accounts setup and each of them "added" user1, user1 accepted each request and all users are visible to user1, but all other users are just like before.

[theARE]

Similar issue - got 3 users set up on my install and I cant find any way of confirming users as friends.

Dragging onto the Gray box for the aspect doesn't work - but dragging them next to the aspect title (e.g. Work) seems to work but when I then click "Update Aspects" Firebug reports the following

POST http://127.0.0.1:3000/aspects/move_friends 500 Internal Server Error 3.56s
jquery...4822439 (line 130)

[madmaze]

Hmm that sounds like a separate Issue, in our problem we can confirm users, but after user2 accepts a friend request from user1, only user2 sees user1 as a friend and user1(the requesting user) sees no addition to his aspect. What OS/Software are you running?

[halfninja]

I think the problem is that dragging and dropping of the friends isn't working. Where @theARE refers to dragging them next to the aspect title, it's just the browser's default image dragging mechanism copying the image into the in-place editor of the aspect title.

[madmaze]

theARE: this may be the fix to your problem(but just a guess): http://github.com/MrZYX/diaspora/commit/d09d3dd8db19a6623e17c48408240684c0a26474

[halfninja]

@madmaze - that change fixed it for me, thanks.

[Mike626]

@madmaze - that change fixed it for me, thanks.

[theARE]

@madmaze - Yeah that fixed the problem thanks. I can now get users to accept each other's friends requests. I cant see what friends are sharing though, but that's a separate issue.

[halfninja]

@theARE - I had that problem until I remembered to start the socket server, that seemed to make viewing others' messages work.

[theARE]

@halfninja - are there instructions on how to do that? I thought I had everything setup but obviously not

[halfninja]

@theARE - yep, the README file! Running script/server starts both a webserver and the socket server, but there's also instructions for starting them separately.

[theARE]

@halfninja - no luck - tarted the socket server fine bundle exec ruby ./script/websocket_server.rb but still cant see friends status updates - this is where the different users are all on the same server.

[halfninja]

@theARE - Not sure then, but some combination of that, serving on port 80 with a proper hostname, and doing rake db:reset sorted it out for me. (Actually, if it's one of them I think it's the port 80 thing.)

[rsofaer]

It sounds like this is worked out, so I'm closing the issue. Thanks everyone!