| Feature Enhancement | Expected in Preview Orgs | Expected in Production Orgs |
|---|---|---|
| Token Preview | December 28, 2017 | January 8, 2017 |
New values for amr base claim | December 28, 2017 | January 8, 2017 |
Configuring an application or integration to use OpenID Connect ID tokens or OAuth 2.0 access tokens can take a lot of trial-and-error. Okta has made it easier to choose configuration settings and see the resulting tokens in the Token Preview tab of the Authorization Server page:

Add values on the left side to see how they would affect the token on the right. All the fields are selection boxes except User. For User, type in the first few letters to see a choice of user names.
You can try out different combinations of values, and see the resulting tokens (or error messages). Once you've got the right combination, it's easy to configure your authorization server and other components.
amr Base Claim We improved some behaviors related for base claim amr:
sms or call are used, the amr claim returns mca.token:hardware is used, the amr claim returns hwk.web is used, the amr claim returns swk. This bug fix is expected in preview orgs starting December 28, 2017 and expected in production orgs starting January 8, 2017.
The following legacy events, already present in the /api/v1/events endpoint, are also available in the /api/v1/logs endpoint (System Log API):
app.auth.slo.with_reasonapp.auth.slo.saml.malformed_request.invalid_typeapp.keys.clone_legacyapp.keys.generate_legacyapp.keys.rotate_legacy