#Moodle error microsoft webmatrix installAfter you've installed the Web Platform Installer, you can use it to install WebMatrix Beta 3. To install WebMatrix Beta 3, you use Microsoft Web Platform Installer 3.0. WebMatrix Beta uses the same powerful web server, database engine, and frameworks environment that will run your website on the internet, which makes the transition from development to production smooth and seamless. You can use WebMatrix Beta to streamline the way you code, test, and publish your own ASP.NET or PHP website, or you can use WebMatrix Beta to start a new website using popular open-source apps like DotNetNuke, Umbraco, WordPress, or Joomla. It integrates a web server with database and programming frameworks to create a single, integrated experience. #Moodle error microsoft webmatrix freeMicrosoft WebMatrix Beta is a free web development stack that installs in minutes. New Features, Changes, and Known Issues in the Beta 3 release Hope that gives a bit of further insight.Web Matrix and ASP.NET Web Pages (Razor) Beta 3 Release Readme This is a relatively fresh install and our first batch of staff being assigned to add content for the next academic year. #Moodle error microsoft webmatrix manualThe second instance was from a user that had tried logging in before their aad account had been synced to moodle (added to our sync group which also applies the enterprise application perms so it appeared in their O365 dashboard before sync had been done).Īs we have create account on sign in turned off it showed ERROR1 and we had an entry in auth_oidc_token that wouldn't correct without manual intervention once they were finally synced and a moodle account created for them to match to. The second time they tried it failed due to the userid field being 0. I believe this user had an IP change half way through logging in (which takes from 5-10 seconds) which ended up incomplete. The first occurrence was during a first login of a user that had already been synced from AAD. I've had two instances of this happen today that had to be manually corrected in the auth_oidc_token table. They then used the msft block to manage their connection and login - no need to change over auth method. Changing this to the "id" value for the user found in xxx_user table fixed the issue. The "userid" field in xxx_auth_oidc_token had the value of zero for some users. It seems like there is some bug when a record originally gets created in the table for a manual-account user - the field userid doesn't get set?Ĭonfirmed, this worked for me. For some reason the auth-method didn't switch, so we did switch it to OpenID manually after the users were matched. Recently they got created in AD and thus they got matched in the sync-job. There were two students that had this problem, and both were originally manual accounts that had never been used and never were created in Azure AD. So I updated the record and magically it work. Looking at the other records in the table, it looked that it matches the unique id in the user table with that username. I looked up the table auth_oidc_token in the database og noticed, that for the record with the correct "username" the field "userid" was empty.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |