Unable to scrape Mazevo scraper with current API key

[mikehquan19]

Overview

As of right now, the Mazevo scraper is not working because the API request returns 401 Unauthorized.

It seems that the request doesn't work with only the API key anymore and would require us to automate the login using Chromedp and get the cookies to make the API call in scrapers/mazevo.go.

Note that Mazevo is behind Duo so we would need to find a way to bypass Duo with Chromedp.

[justinschwerdtfeger]

Putting this here because it may be helpful, to manage duo devices, visit https://uw1.devicemanagement.duosecurity.com/frame/device-management/portal

edit: looks like it doesnt work

[justinschwerdtfeger]

After doing more research, It looks like Mazevo has added "X-Signature" and "X-Timestamp" headers. I'm trying to reverse engineer how they work

[mikehquan19]

Just want to give you my 2 cents that those values seem very short lived. I need to refresh often to get 200 response.

[justinschwerdtfeger]

Yep, that's what I've also found. Looks like I'm going to have to make a ChromeDP scraper, since I can't think of any way without.

[mikehquan19]

Sounds good. Goodbye “api calling with just the key” 🤧

[justinschwerdtfeger]

Good news! I just realized https://east.mymazevo.com/calendar/4219c6df695c03860350ea213837fe59 doesnt require duo, so we can scrape without even being signed in. I've only figured out how to do 1 month at a time, but that should be fine

[mikehquan19]

1 month is ok. You could iterate for 12 months right?

Honestly I don’t see the point of scraping too far into the future. Like the other events scrapers iirc scrape for the next year, with some events even pending

I’m speaking from the UTD rooms perspective but from api perspective maybe people using our api will have loads of data to do something.